Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6f91fdd89dd4b53e8e315e6cfeee6b6a92ca09b411841aad496e6b594ed353

Tx prefix hash: a082926211058dee9a605ef3eeee6d28206d8a324e48381ab5e9421e95532d6b
Tx public key: ab9aba8101a0a444e7412dbee53e3a7b28031761733aa85916d3b5fe38e0fada
Timestamp: 1645573185 Timestamp [UCT]: 2022-02-22 23:39:45 Age [y:d:h:m:s]: 02:282:07:46:47
Block: 444378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721177 RingCT/type: yes/0
Extra: 01ab9aba8101a0a444e7412dbee53e3a7b28031761733aa85916d3b5fe38e0fada021100000001a272b9cb000000000000000000

1 output(s) for total of 20.681950908000 dcy

stealth address amount amount idx
00: a603b4490f925f3eea42ba40ddeb6f28d32fbfa68d5b5ce25abfa4b813a3565c 20.681950908000 857643 of 0

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": 444388, "vin": [ { "gen": { "height": 444378 } } ], "vout": [ { "amount": 20681950908, "target": { "key": "a603b4490f925f3eea42ba40ddeb6f28d32fbfa68d5b5ce25abfa4b813a3565c" } } ], "extra": [ 1, 171, 154, 186, 129, 1, 160, 164, 68, 231, 65, 45, 190, 229, 62, 58, 123, 40, 3, 23, 97, 115, 58, 168, 89, 22, 211, 181, 254, 56, 224, 250, 218, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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