Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b349c1f591b33c5b49cacd943f65f999a262b07b807f18bcfce788b51aee1235

Tx prefix hash: 06df99c9c1a88d1aee8a97ad7627a35c2ec1bdfc9acc60652f5bce3bef12abf8
Tx public key: f069aa9da76e7436c5ed3e4d472430ce1d5753ae3d9617e1a06abf80e87f1f63
Timestamp: 1582512656 Timestamp [UCT]: 2020-02-24 02:50:56 Age [y:d:h:m:s]: 05:009:21:26:14
Block: 71256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160334 RingCT/type: yes/0
Extra: 01f069aa9da76e7436c5ed3e4d472430ce1d5753ae3d9617e1a06abf80e87f1f6302110000000256c366d3000000000000000000

1 output(s) for total of 356.369144156000 dcy

stealth address amount amount idx
00: 5a65798c16ddd11f088e5de7516c66b315ed6dc004162cb1ae88a724dd734fc4 356.369144156000 131656 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": 71266, "vin": [ { "gen": { "height": 71256 } } ], "vout": [ { "amount": 356369144156, "target": { "key": "5a65798c16ddd11f088e5de7516c66b315ed6dc004162cb1ae88a724dd734fc4" } } ], "extra": [ 1, 240, 105, 170, 157, 167, 110, 116, 54, 197, 237, 62, 77, 71, 36, 48, 206, 29, 87, 83, 174, 61, 150, 23, 225, 160, 106, 191, 128, 232, 127, 31, 99, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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