Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94daadd43d380f99e766c509a21baa271b5b17dfaf3b2d152bae6db214272d7d

Tx prefix hash: 68ae3bc19ca053266d44da88b3be61c36490da525a23e269e949a91f1528f01d
Tx public key: 97d760721ae913c9634cadb467b60a14f69b8a4a3de0a909ccf145d132fc161c
Timestamp: 1731442584 Timestamp [UCT]: 2024-11-12 20:16:24 Age [y:d:h:m:s]: 00:147:04:22:04
Block: 1152317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105025 RingCT/type: yes/0
Extra: 0197d760721ae913c9634cadb467b60a14f69b8a4a3de0a909ccf145d132fc161c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 835a5e8b6cf83cc444003326dc680f2a5a6c77e3bfd0c034ff8ece2bf4e0f77e 0.600000000000 1637912 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": 1152327, "vin": [ { "gen": { "height": 1152317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "835a5e8b6cf83cc444003326dc680f2a5a6c77e3bfd0c034ff8ece2bf4e0f77e" } } ], "extra": [ 1, 151, 215, 96, 114, 26, 233, 19, 201, 99, 76, 173, 180, 103, 182, 10, 20, 246, 155, 138, 74, 61, 224, 169, 9, 204, 241, 69, 209, 50, 252, 22, 28, 2, 17, 0, 0, 0, 4, 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