Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e54c857fbe9ca7861c66576b488896a5099dbc21df5ee36d4e8af403e728cd8

Tx prefix hash: 57b113233487ca4c23b9bb917977e66fc633813669aa4e196cd3de2d0fc13ab5
Tx public key: a952c6d1d0a633d0c8f499652c75b6e4e3e7a7a176400946300fcf1ff2ac3270
Timestamp: 1766231341 Timestamp [UCT]: 2025-12-20 11:49:01 Age [y:d:h:m:s]: 00:001:02:44:13
Block: 1437703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 790 RingCT/type: yes/0
Extra: 01a952c6d1d0a633d0c8f499652c75b6e4e3e7a7a176400946300fcf1ff2ac32700211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23ef8b905103ccfd0265a33f380f008639531214489825595abef5d4e50e35be 0.600000000000 1926514 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": 1437713, "vin": [ { "gen": { "height": 1437703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23ef8b905103ccfd0265a33f380f008639531214489825595abef5d4e50e35be" } } ], "extra": [ 1, 169, 82, 198, 209, 208, 166, 51, 208, 200, 244, 153, 101, 44, 117, 182, 228, 227, 231, 167, 161, 118, 64, 9, 70, 48, 15, 207, 31, 242, 172, 50, 112, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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