Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4e5e0d3e559834d26ed5150002296c2f513c6bdbd12bfdfeaec59e2edb646ed

Tx prefix hash: 00787464deefffbd4f3f979f2ebbf95680f61ad9ad122cf44982491670563c78
Tx public key: 661329e99dc3b4f412d714a5cb9f10d0eba67b12a524af1dae9cbba6d5632381
Timestamp: 1741251090 Timestamp [UCT]: 2025-03-06 08:51:30 Age [y:d:h:m:s]: 00:260:14:33:41
Block: 1233278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183997 RingCT/type: yes/0
Extra: 01661329e99dc3b4f412d714a5cb9f10d0eba67b12a524af1dae9cbba6d5632381021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fab3be5930724a3bd1461a9cf8dc5cadf53e7e640e36cc198e04300ebb56e56 0.600000000000 1720197 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": 1233288, "vin": [ { "gen": { "height": 1233278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fab3be5930724a3bd1461a9cf8dc5cadf53e7e640e36cc198e04300ebb56e56" } } ], "extra": [ 1, 102, 19, 41, 233, 157, 195, 180, 244, 18, 215, 20, 165, 203, 159, 16, 208, 235, 166, 123, 18, 165, 36, 175, 29, 174, 156, 187, 166, 213, 99, 35, 129, 2, 17, 0, 0, 0, 3, 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