Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c8ef42b21e69a28c5c0a2bb38ca44cf3f0341998dca0ae34f0276c522a8fbe

Tx prefix hash: 48e2f3fd151b07e2dac0d54252aea59796b04fe31be1efe8cf1b9ea6c2c6ad1c
Tx public key: 10d84740362568fd324f052b73b3b4474328c58fdc2f783dc491cb9e74bdbb35
Timestamp: 1721776311 Timestamp [UCT]: 2024-07-23 23:11:51 Age [y:d:h:m:s]: 00:182:15:42:36
Block: 1072275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130649 RingCT/type: yes/0
Extra: 0110d84740362568fd324f052b73b3b4474328c58fdc2f783dc491cb9e74bdbb35021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47ae15b62edc30e62bf6ef43e4ab7f244dd4d12d186780b9cba1b3a8ecce08f8 0.600000000000 1544736 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": 1072285, "vin": [ { "gen": { "height": 1072275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47ae15b62edc30e62bf6ef43e4ab7f244dd4d12d186780b9cba1b3a8ecce08f8" } } ], "extra": [ 1, 16, 216, 71, 64, 54, 37, 104, 253, 50, 79, 5, 43, 115, 179, 180, 71, 67, 40, 197, 143, 220, 47, 120, 61, 196, 145, 203, 158, 116, 189, 187, 53, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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