Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5db2150081572a45a489a94796ceb9acede4e428d724c2240a1b147ec1dae63a

Tx prefix hash: 5d1495f524b401456291e8ac9d40fdfb94a5d812b5c7eccc581ffb9ba5469fed
Tx public key: 220d1caf7a494aacfc13137b96aa16a1a5f840e2bed1a3ba5cfbd299387554de
Timestamp: 1646644894 Timestamp [UCT]: 2022-03-07 09:21:34 Age [y:d:h:m:s]: 02:291:19:11:53
Block: 453163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728068 RingCT/type: yes/0
Extra: 01220d1caf7a494aacfc13137b96aa16a1a5f840e2bed1a3ba5cfbd299387554de0211000000094da16a3a000000000000000000

1 output(s) for total of 19.341187637000 dcy

stealth address amount amount idx
00: 7bbcdbe121dfeda156a4ceecbdf2d1ec9d1e273e6271afbf416bd58a1e3eca04 19.341187637000 868590 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": 453173, "vin": [ { "gen": { "height": 453163 } } ], "vout": [ { "amount": 19341187637, "target": { "key": "7bbcdbe121dfeda156a4ceecbdf2d1ec9d1e273e6271afbf416bd58a1e3eca04" } } ], "extra": [ 1, 34, 13, 28, 175, 122, 73, 74, 172, 252, 19, 19, 123, 150, 170, 22, 161, 165, 248, 64, 226, 190, 209, 163, 186, 92, 251, 210, 153, 56, 117, 84, 222, 2, 17, 0, 0, 0, 9, 77, 161, 106, 58, 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