Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b8ec0cc62c7ceea725db139385cb4b55e74a21ef2f0042e6ac57b8570df9bb

Tx prefix hash: f36ad87558c76b59552191bfe730de8400ff0d9e2f483410575e9f33d8fc709f
Tx public key: 6778f3a2e39b79d730b9441f894528d7301cc1ddbf1ff743118e412b947d65da
Timestamp: 1736598454 Timestamp [UCT]: 2025-01-11 12:27:34 Age [y:d:h:m:s]: 00:344:12:43:24
Block: 1195020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243798 RingCT/type: yes/0
Extra: 016778f3a2e39b79d730b9441f894528d7301cc1ddbf1ff743118e412b947d65da0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8bf270cf66f5a27238d5c6b75508b8cadd0dee829e72c81ae86a44bbc0ff7ff 0.600000000000 1681605 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": 1195030, "vin": [ { "gen": { "height": 1195020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8bf270cf66f5a27238d5c6b75508b8cadd0dee829e72c81ae86a44bbc0ff7ff" } } ], "extra": [ 1, 103, 120, 243, 162, 227, 155, 121, 215, 48, 185, 68, 31, 137, 69, 40, 215, 48, 28, 193, 221, 191, 31, 247, 67, 17, 142, 65, 43, 148, 125, 101, 218, 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