Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a25d332d37299e4fb18cddc9f372aff84ab0d11f0826628e62abb580da3d3381

Tx prefix hash: d9b0af249878e1242181b5ec5ad7d678fc1941de1b06897c0955006887f998f4
Tx public key: 5cb970fb84bfc6d4b26478ff8e5d9cdd529f301e6b0534601e1e3a7932f24cec
Timestamp: 1702441713 Timestamp [UCT]: 2023-12-13 04:28:33 Age [y:d:h:m:s]: 01:148:00:01:59
Block: 912008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366905 RingCT/type: yes/0
Extra: 015cb970fb84bfc6d4b26478ff8e5d9cdd529f301e6b0534601e1e3a7932f24cec02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7a5900f445847f7242adaa1052e0131915b6c9d39f1fef128d44acada63a696 0.600000000000 1369226 of 15

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": 912018, "vin": [ { "gen": { "height": 912008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7a5900f445847f7242adaa1052e0131915b6c9d39f1fef128d44acada63a696" } } ], "extra": [ 1, 92, 185, 112, 251, 132, 191, 198, 212, 178, 100, 120, 255, 142, 93, 156, 221, 82, 159, 48, 30, 107, 5, 52, 96, 30, 30, 58, 121, 50, 242, 76, 236, 2, 17, 0, 0, 0, 2, 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