Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa212958df9883723cc15e61a777863467e4efa3ffaa96990876cb5aa3ebae1f

Tx prefix hash: f9a98a5cf74eed5474d4895daaf37bc62c67e661e1d1b5c3898a96f5ca07dab9
Tx public key: 2481d4a5bba121f9b6b6d0c6b7725fe64d9d4500559a43798e47fe0ced7242ec
Timestamp: 1699715267 Timestamp [UCT]: 2023-11-11 15:07:47 Age [y:d:h:m:s]: 01:362:16:49:11
Block: 889388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518127 RingCT/type: yes/0
Extra: 012481d4a5bba121f9b6b6d0c6b7725fe64d9d4500559a43798e47fe0ced7242ec0211000000014b8f5122000000000000000000

1 output(s) for total of 0.693566890000 dcy

stealth address amount amount idx
00: 18154a85c15779a210f4140e5a8bb9bfeb31b54bbe01c6e9bbddeebef9c4a4d5 0.693566890000 1345385 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": 889398, "vin": [ { "gen": { "height": 889388 } } ], "vout": [ { "amount": 693566890, "target": { "key": "18154a85c15779a210f4140e5a8bb9bfeb31b54bbe01c6e9bbddeebef9c4a4d5" } } ], "extra": [ 1, 36, 129, 212, 165, 187, 161, 33, 249, 182, 182, 208, 198, 183, 114, 95, 230, 77, 157, 69, 0, 85, 154, 67, 121, 142, 71, 254, 12, 237, 114, 66, 236, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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