Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98829d1781d7b62ec1f3160248fa25b077a441170ee7fac2a1b0ce6fb08ff551

Tx prefix hash: e0cac8a43201275e37df8f406043189ebd9aef2a4b8fad4867b692c65759a5e7
Tx public key: 007c891252fd73e8fa048368023114ff8faf5a5cc38d960d8e16012bd21537d2
Timestamp: 1607783352 Timestamp [UCT]: 2020-12-12 14:29:12 Age [y:d:h:m:s]: 04:151:21:25:20
Block: 160676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120610 RingCT/type: yes/0
Extra: 01007c891252fd73e8fa048368023114ff8faf5a5cc38d960d8e16012bd21537d20211000003c14ea414e5000000000000000000

1 output(s) for total of 180.141755912000 dcy

stealth address amount amount idx
00: bdd0fafa2dbacdeade5b7efb530dc12e6748d6d82f84d34c9b58c092e853801d 180.141755912000 283432 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": 160686, "vin": [ { "gen": { "height": 160676 } } ], "vout": [ { "amount": 180141755912, "target": { "key": "bdd0fafa2dbacdeade5b7efb530dc12e6748d6d82f84d34c9b58c092e853801d" } } ], "extra": [ 1, 0, 124, 137, 18, 82, 253, 115, 232, 250, 4, 131, 104, 2, 49, 20, 255, 143, 175, 90, 92, 195, 141, 150, 13, 142, 22, 1, 43, 210, 21, 55, 210, 2, 17, 0, 0, 3, 193, 78, 164, 20, 229, 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