Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b584c61bfa922f75ee81efb2a8be8f9def2697c1d6dfda5d3af5fa575c9aaa9

Tx prefix hash: 70075b6ee909d70cafac00af253bd83f0bad442f58dee3acf574a2476a4ebbba
Tx public key: 0cc6ac763f7256eac6194802fcaa22bb5041eecf75e21d9a16c810d15a3b7981
Timestamp: 1703581452 Timestamp [UCT]: 2023-12-26 09:04:12 Age [y:d:h:m:s]: 01:121:02:47:13
Block: 921437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347696 RingCT/type: yes/0
Extra: 010cc6ac763f7256eac6194802fcaa22bb5041eecf75e21d9a16c810d15a3b79810211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4f0748ee5443bbfd5b7c48bac5f293fb2f39ffe5ba04728bf6fc4e935dc7988 0.600000000000 1379125 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": 921447, "vin": [ { "gen": { "height": 921437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4f0748ee5443bbfd5b7c48bac5f293fb2f39ffe5ba04728bf6fc4e935dc7988" } } ], "extra": [ 1, 12, 198, 172, 118, 63, 114, 86, 234, 198, 25, 72, 2, 252, 170, 34, 187, 80, 65, 238, 207, 117, 226, 29, 154, 22, 200, 16, 209, 90, 59, 121, 129, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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