Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fba7768d6814ae589712b009f47d12ea2d069312514f8f8b51ac378e4f75afa2

Tx prefix hash: 66f38020dcfee041bd474b476a7e6e86a283df4fa275d0f291540339d79d1cc6
Tx public key: e80a3307931a007348d20952782e5d691effbf4825a4dc8dd800af3c4e74756e
Timestamp: 1577428378 Timestamp [UCT]: 2019-12-27 06:32:58 Age [y:d:h:m:s]: 05:006:19:42:09
Block: 32709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154850 RingCT/type: yes/0
Extra: 01e80a3307931a007348d20952782e5d691effbf4825a4dc8dd800af3c4e74756e0211000000134ac5aa02000000000000000000

1 output(s) for total of 478.222334752000 dcy

stealth address amount amount idx
00: c91391d6b58fd3ca772989401fb4476ea701d95418cbf6e1f96d0c0de14d7053 478.222334752000 54466 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": 32719, "vin": [ { "gen": { "height": 32709 } } ], "vout": [ { "amount": 478222334752, "target": { "key": "c91391d6b58fd3ca772989401fb4476ea701d95418cbf6e1f96d0c0de14d7053" } } ], "extra": [ 1, 232, 10, 51, 7, 147, 26, 0, 115, 72, 210, 9, 82, 120, 46, 93, 105, 30, 255, 191, 72, 37, 164, 220, 141, 216, 0, 175, 60, 78, 116, 117, 110, 2, 17, 0, 0, 0, 19, 74, 197, 170, 2, 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