Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67c7af9a3d992c9ce4b197e5b670eb79f2ae09ce05fb062636fef6b0515e9744

Tx prefix hash: b74f2f4b824aa38fab30ace0c213717bc87386631bf0d8f4ddfb2aca3d8eeb16
Tx public key: cd479bd4004720d0d1af5dbc248ee93c12da0f5f2159c4a13c57dc670d84bfde
Timestamp: 1673795337 Timestamp [UCT]: 2023-01-15 15:08:57 Age [y:d:h:m:s]: 02:092:13:00:15
Block: 675353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587815 RingCT/type: yes/0
Extra: 01cd479bd4004720d0d1af5dbc248ee93c12da0f5f2159c4a13c57dc670d84bfde0211000000028b7b6602000000000000000000

1 output(s) for total of 3.550382204000 dcy

stealth address amount amount idx
00: 0574df40d598f9880618e4b14496a48e2a0c981266652f86851327817a716fce 3.550382204000 1117028 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": 675363, "vin": [ { "gen": { "height": 675353 } } ], "vout": [ { "amount": 3550382204, "target": { "key": "0574df40d598f9880618e4b14496a48e2a0c981266652f86851327817a716fce" } } ], "extra": [ 1, 205, 71, 155, 212, 0, 71, 32, 208, 209, 175, 93, 188, 36, 142, 233, 60, 18, 218, 15, 95, 33, 89, 196, 161, 60, 87, 220, 103, 13, 132, 191, 222, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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