Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0592a4533f88d3528190634c22adfd677a0d3ba1b92eded91df9e09bb3cf13

Tx prefix hash: a14cb4d946d6129515ec447147ced6046cd0234290c94ae2d5fb956fb93ba963
Tx public key: 93da4b49de7ce351e3bff8a85969bdadb1ab2221b30b8c2aae1e5c725c32ba28
Timestamp: 1734482810 Timestamp [UCT]: 2024-12-18 00:46:50 Age [y:d:h:m:s]: 00:330:21:20:57
Block: 1177542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233971 RingCT/type: yes/0
Extra: 0193da4b49de7ce351e3bff8a85969bdadb1ab2221b30b8c2aae1e5c725c32ba280211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7077c7d5fa1131eb5237de2f85bc768aaca337d64ae01eac1acff3475e1c72d3 0.600000000000 1663913 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": 1177552, "vin": [ { "gen": { "height": 1177542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7077c7d5fa1131eb5237de2f85bc768aaca337d64ae01eac1acff3475e1c72d3" } } ], "extra": [ 1, 147, 218, 75, 73, 222, 124, 227, 81, 227, 191, 248, 168, 89, 105, 189, 173, 177, 171, 34, 33, 179, 11, 140, 42, 174, 30, 92, 114, 92, 50, 186, 40, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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