Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d22e6d1fa30c22d5f5d681a8854aeafff47b0f45166adf3b17f835b26d2db6ce

Tx prefix hash: 5cc544b24be7bc73d471db159dc84a0eb12dbce5d27bf5f80408b12ef3f6eb9d
Tx public key: 66541fd7fb445a6eb00ac7b26a6f7eff9bb6d65027f23f4a5515c63440ad02e4
Timestamp: 1736721360 Timestamp [UCT]: 2025-01-12 22:36:00 Age [y:d:h:m:s]: 00:156:12:46:54
Block: 1196037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111581 RingCT/type: yes/0
Extra: 0166541fd7fb445a6eb00ac7b26a6f7eff9bb6d65027f23f4a5515c63440ad02e4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76d48a2ce55225f1f1abb156164f58ef04528477221262cddbeafb44c53a3ff2 0.600000000000 1682634 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1196047, "vin": [ { "gen": { "height": 1196037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76d48a2ce55225f1f1abb156164f58ef04528477221262cddbeafb44c53a3ff2" } } ], "extra": [ 1, 102, 84, 31, 215, 251, 68, 90, 110, 176, 10, 199, 178, 106, 111, 126, 255, 155, 182, 214, 80, 39, 242, 63, 74, 85, 21, 198, 52, 64, 173, 2, 228, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8