Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec6831a2b6522465a1179a736f0f6526fca7eda2b91efce4628b3b37bc2c56b3

Tx prefix hash: f370708ef8468c125ede5ded33870551b049efc3aae8461121e98fd077f1b83b
Tx public key: 6ded0b4bc63c852b8e56d0d5a75ab6153748cae237ea80ec91aeaa97bf9e6d2d
Timestamp: 1732142400 Timestamp [UCT]: 2024-11-20 22:40:00 Age [y:d:h:m:s]: 00:000:12:45:22
Block: 1158118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386 RingCT/type: yes/0
Extra: 016ded0b4bc63c852b8e56d0d5a75ab6153748cae237ea80ec91aeaa97bf9e6d2d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e06b84559c43715953ac3a1d5112e484fc07856e906cd7b64d50e35aa79080a 0.600000000000 1643747 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": 1158128, "vin": [ { "gen": { "height": 1158118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e06b84559c43715953ac3a1d5112e484fc07856e906cd7b64d50e35aa79080a" } } ], "extra": [ 1, 109, 237, 11, 75, 198, 60, 133, 43, 142, 86, 208, 213, 167, 90, 182, 21, 55, 72, 202, 226, 55, 234, 128, 236, 145, 174, 170, 151, 191, 158, 109, 45, 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