Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fb363c3c88d1b0831d9e0d2421f6cd7cfe6ac1e42fae2592157118a41362e6

Tx prefix hash: efbaf321009ee5142bba18803ff8a3e48f523381a3b8261edabef8f66ad85e75
Tx public key: 7f35411a4e5cf80c02630f97ccdf9c74c51102005c22f1e534cedd4abfecad0a
Timestamp: 1724602256 Timestamp [UCT]: 2024-08-25 16:10:56 Age [y:d:h:m:s]: 00:133:16:09:55
Block: 1095718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95616 RingCT/type: yes/0
Extra: 017f35411a4e5cf80c02630f97ccdf9c74c51102005c22f1e534cedd4abfecad0a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b25b776df5c8e35162511cf708b0fb1bf79518d8a29862b65d1b47e4c166fc 0.600000000000 1570899 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": 1095728, "vin": [ { "gen": { "height": 1095718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b25b776df5c8e35162511cf708b0fb1bf79518d8a29862b65d1b47e4c166fc" } } ], "extra": [ 1, 127, 53, 65, 26, 78, 92, 248, 12, 2, 99, 15, 151, 204, 223, 156, 116, 197, 17, 2, 0, 92, 34, 241, 229, 52, 206, 221, 74, 191, 236, 173, 10, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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