Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45cc56534fb126472ee543a69af52211724d8f09c9b5f21eb5a7cc818862532

Tx prefix hash: 1864f07b99d2415ebff7d1ee49c8b911742a55b1ed58e4e851cf97b0dace01ac
Tx public key: fb97dcc06c9a896b5f070f9cdb31acd28d4f937c11149dac1cc3f8c9a598c86f
Timestamp: 1745202895 Timestamp [UCT]: 2025-04-21 02:34:55 Age [y:d:h:m:s]: 00:192:13:24:53
Block: 1265967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135343 RingCT/type: yes/0
Extra: 01fb97dcc06c9a896b5f070f9cdb31acd28d4f937c11149dac1cc3f8c9a598c86f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88f0bb3b7bb06b540e08be00a571ac0871316be9f5957204b99710e6bd44b937 0.600000000000 1753180 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": 1265977, "vin": [ { "gen": { "height": 1265967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88f0bb3b7bb06b540e08be00a571ac0871316be9f5957204b99710e6bd44b937" } } ], "extra": [ 1, 251, 151, 220, 192, 108, 154, 137, 107, 95, 7, 15, 156, 219, 49, 172, 210, 141, 79, 147, 124, 17, 20, 157, 172, 28, 195, 248, 201, 165, 152, 200, 111, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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