Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd712ea210217ac229c473028c6d386841723ef604a91774521a68167c404250

Tx prefix hash: 453994c86298781c157948f1c0ea1f548b1e35ff1e7254421ec31a7ae0580118
Tx public key: 3d2a588e42524fbc1f88e3b9327b8f8b334c2b598692a1ec8b25f0662eeee461
Timestamp: 1697404818 Timestamp [UCT]: 2023-10-15 21:20:18 Age [y:d:h:m:s]: 01:226:12:16:17
Block: 870434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422968 RingCT/type: yes/0
Extra: 013d2a588e42524fbc1f88e3b9327b8f8b334c2b598692a1ec8b25f0662eeee46102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.801476606000 dcy

stealth address amount amount idx
00: 57a34d3eced7b48adc29c522e5e4c7ab36283f01022407a38f98aa079239fe9d 0.801476606000 1325313 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": 870444, "vin": [ { "gen": { "height": 870434 } } ], "vout": [ { "amount": 801476606, "target": { "key": "57a34d3eced7b48adc29c522e5e4c7ab36283f01022407a38f98aa079239fe9d" } } ], "extra": [ 1, 61, 42, 88, 142, 66, 82, 79, 188, 31, 136, 227, 185, 50, 123, 143, 139, 51, 76, 43, 89, 134, 146, 161, 236, 139, 37, 240, 102, 46, 238, 228, 97, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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