Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d003901363f3bd24ab3107a6c7ce5a37e4f9b2516c2539168c5e9d86a17728

Tx prefix hash: 93ef683bc6cb908aee67c0dbb17899099a0f9bf6f0b50b6452add102f0353003
Tx public key: 1ee0b598abd423d1df687ae7712c54be75988f75cfc91c8314fd9f3df7fced2f
Timestamp: 1583005292 Timestamp [UCT]: 2020-02-29 19:41:32 Age [y:d:h:m:s]: 04:314:15:55:35
Block: 74355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118496 RingCT/type: yes/0
Extra: 011ee0b598abd423d1df687ae7712c54be75988f75cfc91c8314fd9f3df7fced2f0211000000700aca7173000000000000000000

1 output(s) for total of 348.042129308000 dcy

stealth address amount amount idx
00: 1d61a3eac830fe0bce06250cac4f23d219c3bf2a7f4e257d2fb28bc5d7b2c1ca 348.042129308000 137553 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": 74365, "vin": [ { "gen": { "height": 74355 } } ], "vout": [ { "amount": 348042129308, "target": { "key": "1d61a3eac830fe0bce06250cac4f23d219c3bf2a7f4e257d2fb28bc5d7b2c1ca" } } ], "extra": [ 1, 30, 224, 181, 152, 171, 212, 35, 209, 223, 104, 122, 231, 113, 44, 84, 190, 117, 152, 143, 117, 207, 201, 28, 131, 20, 253, 159, 61, 247, 252, 237, 47, 2, 17, 0, 0, 0, 112, 10, 202, 113, 115, 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