Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddf8980b2bf65b68da81ee535f54ba5bca9d17fea276dae80384ab53090636ff

Tx prefix hash: 245ad9da15890ae1ac964140edac77c1f710eab19d5aa734b01f6c47492cb905
Tx public key: 3d1e8637dc8fef1e20bac01ae6d65076adf3e96f865701d919883460224f4338
Timestamp: 1696123186 Timestamp [UCT]: 2023-10-01 01:19:46 Age [y:d:h:m:s]: 01:199:06:23:03
Block: 859807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403467 RingCT/type: yes/0
Extra: 013d1e8637dc8fef1e20bac01ae6d65076adf3e96f865701d919883460224f433802110000000875e3f0e9000000000000000000

1 output(s) for total of 0.869165598000 dcy

stealth address amount amount idx
00: 7ebf9d085877bcb9e8057c0ebdb2123fb905150e6c4195870ef83427ffbca282 0.869165598000 1314053 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": 859817, "vin": [ { "gen": { "height": 859807 } } ], "vout": [ { "amount": 869165598, "target": { "key": "7ebf9d085877bcb9e8057c0ebdb2123fb905150e6c4195870ef83427ffbca282" } } ], "extra": [ 1, 61, 30, 134, 55, 220, 143, 239, 30, 32, 186, 192, 26, 230, 214, 80, 118, 173, 243, 233, 111, 134, 87, 1, 217, 25, 136, 52, 96, 34, 79, 67, 56, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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