Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa2feae988851891ac262b185449669ea6081ba7bcdb2df735f1dcc04761812

Tx prefix hash: 85e150a93a40e8826e70be1826e8595d6a508a6aef8cd742e9135f5c3ebe220d
Tx public key: 0f0e8ce3c4f1047641dfde1663e0669ac5ef7ed8fe00af128386aed83e9255e9
Timestamp: 1648846480 Timestamp [UCT]: 2022-04-01 20:54:40 Age [y:d:h:m:s]: 02:243:21:45:45
Block: 471170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694000 RingCT/type: yes/0
Extra: 010f0e8ce3c4f1047641dfde1663e0669ac5ef7ed8fe00af128386aed83e9255e9021100000002a8c141c5000000000000000000

1 output(s) for total of 16.858481193000 dcy

stealth address amount amount idx
00: 9679e345c90f2e92970d3b6d9a9ea7858cb5b2bb0e2c1c9f1882ac0a46ec737d 16.858481193000 890456 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": 471180, "vin": [ { "gen": { "height": 471170 } } ], "vout": [ { "amount": 16858481193, "target": { "key": "9679e345c90f2e92970d3b6d9a9ea7858cb5b2bb0e2c1c9f1882ac0a46ec737d" } } ], "extra": [ 1, 15, 14, 140, 227, 196, 241, 4, 118, 65, 223, 222, 22, 99, 224, 102, 154, 197, 239, 126, 216, 254, 0, 175, 18, 131, 134, 174, 216, 62, 146, 85, 233, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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