Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03de0d6ae8846c3ef04355e1a105a1a16827b468e42d06b1ec317d1f047ea9d9

Tx prefix hash: b97b6e10b147f5192df1841c5dbf3d6924e120acb867e2ad98b1c3514c341e86
Tx public key: 0afc6321d8c8b82009f5ba7030efa8180fbf9b52f2dacb534233cd29995c573a
Timestamp: 1733332427 Timestamp [UCT]: 2024-12-04 17:13:47 Age [y:d:h:m:s]: 00:109:21:11:32
Block: 1167984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78332 RingCT/type: yes/0
Extra: 010afc6321d8c8b82009f5ba7030efa8180fbf9b52f2dacb534233cd29995c573a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edc50d55f465d078d32d812ae962cbad3092a6dd3584c28acaef24d58db6c598 0.600000000000 1653689 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": 1167994, "vin": [ { "gen": { "height": 1167984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edc50d55f465d078d32d812ae962cbad3092a6dd3584c28acaef24d58db6c598" } } ], "extra": [ 1, 10, 252, 99, 33, 216, 200, 184, 32, 9, 245, 186, 112, 48, 239, 168, 24, 15, 191, 155, 82, 242, 218, 203, 83, 66, 51, 205, 41, 153, 92, 87, 58, 2, 17, 0, 0, 0, 2, 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