Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea0bfd7f7ddf7c47c1dd5cf9a0e9916856b43cdd6cd804925598c555c8306ab3

Tx prefix hash: ec202edd945c3d3c1a8c194f17e9733906f7eea1f48102f01d4166040b5b4f1e
Tx public key: 200114cb28d0fb115b996b5d49467dbda143867d82d713de8a5ebb5222f2c66e
Timestamp: 1755371875 Timestamp [UCT]: 2025-08-16 19:17:55 Age [y:d:h:m:s]: 00:096:22:50:04
Block: 1348007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69111 RingCT/type: yes/0
Extra: 01200114cb28d0fb115b996b5d49467dbda143867d82d713de8a5ebb5222f2c66e021100000006e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5d6721ddd3a3e385e4b4b4e7394f3479a5f57b754e9dd50f6af0d1adec90e8b 0.600000000000 1835930 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": 1348017, "vin": [ { "gen": { "height": 1348007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5d6721ddd3a3e385e4b4b4e7394f3479a5f57b754e9dd50f6af0d1adec90e8b" } } ], "extra": [ 1, 32, 1, 20, 203, 40, 208, 251, 17, 91, 153, 107, 93, 73, 70, 125, 189, 161, 67, 134, 125, 130, 215, 19, 222, 138, 94, 187, 82, 34, 242, 198, 110, 2, 17, 0, 0, 0, 6, 228, 220, 144, 9, 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