Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f05593ef2e3227e2a7ff8f0354cf92295b313e9d463d76f39c82cb59f45df26

Tx prefix hash: adec0602e0b9d4aa4c222d39df69c5af31359833656a5941eac51aa2b138b739
Tx public key: 3a8255befb453f7bd682298ae1d88dc0494615e7d40af10b25875c916b10036f
Timestamp: 1716213338 Timestamp [UCT]: 2024-05-20 13:55:38 Age [y:d:h:m:s]: 00:312:23:57:52
Block: 1026164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223708 RingCT/type: yes/0
Extra: 013a8255befb453f7bd682298ae1d88dc0494615e7d40af10b25875c916b10036f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a079035b309d590028d50b4e6dbfdb458107c837ab253906b3c02fe69578f96a 0.600000000000 1493097 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": 1026174, "vin": [ { "gen": { "height": 1026164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a079035b309d590028d50b4e6dbfdb458107c837ab253906b3c02fe69578f96a" } } ], "extra": [ 1, 58, 130, 85, 190, 251, 69, 63, 123, 214, 130, 41, 138, 225, 216, 141, 192, 73, 70, 21, 231, 212, 10, 241, 11, 37, 135, 92, 145, 107, 16, 3, 111, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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