Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ff3f05b8d9c39d9e1489462384aaa267c2324a6c377baae61b22bcfd327349

Tx prefix hash: 1223a6c4430fcbfd45500f7d621be1e949b0c42336b02d3d45416101e5af37cb
Tx public key: 56b41dbe024104f797ed36b5bed71fd6a26b8ef12e5661bb30c3e0808c089803
Timestamp: 1709385847 Timestamp [UCT]: 2024-03-02 13:24:07 Age [y:d:h:m:s]: 00:340:04:45:33
Block: 969561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243249 RingCT/type: yes/0
Extra: 0156b41dbe024104f797ed36b5bed71fd6a26b8ef12e5661bb30c3e0808c0898030211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d5f9265d8f7d472f2f0d369a14f0ad8c4c139c4ea363ce8f96792ea18458f11 0.600000000000 1429398 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": 969571, "vin": [ { "gen": { "height": 969561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d5f9265d8f7d472f2f0d369a14f0ad8c4c139c4ea363ce8f96792ea18458f11" } } ], "extra": [ 1, 86, 180, 29, 190, 2, 65, 4, 247, 151, 237, 54, 181, 190, 215, 31, 214, 162, 107, 142, 241, 46, 86, 97, 187, 48, 195, 224, 128, 140, 8, 152, 3, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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