Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47104e4fc25fa1d76d956f1c43c6bbcfd2ef0629bfadf23e81c5905a9ee1bdf5

Tx prefix hash: 96a63143b8140d84de3e9d00df22f1461bcb968cc584666d2df50b28dcd6cf4e
Tx public key: 2a62e9f0723fc53fa36ffe465f223fa41f3ca6d0a3203b80fc3b7c62de3bea7a
Timestamp: 1703361642 Timestamp [UCT]: 2023-12-23 20:00:42 Age [y:d:h:m:s]: 01:120:14:50:48
Block: 919612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347340 RingCT/type: yes/0
Extra: 012a62e9f0723fc53fa36ffe465f223fa41f3ca6d0a3203b80fc3b7c62de3bea7a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adc7b7f3297678aa66553c7a755dff1fec6eca6792da6c715c03324498845512 0.600000000000 1377288 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": 919622, "vin": [ { "gen": { "height": 919612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adc7b7f3297678aa66553c7a755dff1fec6eca6792da6c715c03324498845512" } } ], "extra": [ 1, 42, 98, 233, 240, 114, 63, 197, 63, 163, 111, 254, 70, 95, 34, 63, 164, 31, 60, 166, 208, 163, 32, 59, 128, 252, 59, 124, 98, 222, 59, 234, 122, 2, 17, 0, 0, 0, 4, 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