Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dadbcd04594a4514aa9e573807bf887b3dab10f6c9cb1f4439ab9cb668c9785

Tx prefix hash: a313f82796eb545292ccab5f04bfd43de10c743860365951e001b712904d490c
Tx public key: f80fcc9ec2b8f00bc2c906a14edf536cb40201c8b7856a7f72f927e7c48a368d
Timestamp: 1706420177 Timestamp [UCT]: 2024-01-28 05:36:17 Age [y:d:h:m:s]: 00:291:10:48:46
Block: 944950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208705 RingCT/type: yes/0
Extra: 01f80fcc9ec2b8f00bc2c906a14edf536cb40201c8b7856a7f72f927e7c48a368d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e88b2f8654ad2eb6fe296197de06ed5e94ebfd1f918694ee92dea6cce43e70a4 0.600000000000 1403252 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": 944960, "vin": [ { "gen": { "height": 944950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e88b2f8654ad2eb6fe296197de06ed5e94ebfd1f918694ee92dea6cce43e70a4" } } ], "extra": [ 1, 248, 15, 204, 158, 194, 184, 240, 11, 194, 201, 6, 161, 78, 223, 83, 108, 180, 2, 1, 200, 183, 133, 106, 127, 114, 249, 39, 231, 196, 138, 54, 141, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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