Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a88f1f222ebdc61ff3e70e9310c237bc6caf05cc9620c5944771afdaee1e6018

Tx prefix hash: 1fb9574c6b417dfb979d25b5122e78560eb6fc684a026302e30cc84c702eef83
Tx public key: 590b8fbcae8eb19c921b8415a33fafa791bf2b500f850d59e787a64b86d3d94c
Timestamp: 1584924551 Timestamp [UCT]: 2020-03-23 00:49:11 Age [y:d:h:m:s]: 05:227:01:38:32
Block: 87085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1317394 RingCT/type: yes/0
Extra: 01590b8fbcae8eb19c921b8415a33fafa791bf2b500f850d59e787a64b86d3d94c02110000009669b04ac4000000000000000000

1 output(s) for total of 315.829013556000 dcy

stealth address amount amount idx
00: f68a159d5785ca47f6a3ea18da0fd996c4cc159059fd27bc7853700af6d2342e 315.829013556000 157001 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": 87095, "vin": [ { "gen": { "height": 87085 } } ], "vout": [ { "amount": 315829013556, "target": { "key": "f68a159d5785ca47f6a3ea18da0fd996c4cc159059fd27bc7853700af6d2342e" } } ], "extra": [ 1, 89, 11, 143, 188, 174, 142, 177, 156, 146, 27, 132, 21, 163, 63, 175, 167, 145, 191, 43, 80, 15, 133, 13, 89, 231, 135, 166, 75, 134, 211, 217, 76, 2, 17, 0, 0, 0, 150, 105, 176, 74, 196, 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