Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4c9544606147329f5a4db4ddee4e5988e7e3e979711ece2f8ef1b1e00445b4

Tx prefix hash: 17f5d766a6cb21ca9bc4353e96b5fd3b4c7c94af3b1b8fff38f6e8340bbdbf3e
Tx public key: 7a66c668d4409cb4b312eec8ac4e5a420b6d2ead06b20944017b8d11eb0f362c
Timestamp: 1729090048 Timestamp [UCT]: 2024-10-16 14:47:28 Age [y:d:h:m:s]: 00:084:11:08:44
Block: 1132934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60349 RingCT/type: yes/0
Extra: 017a66c668d4409cb4b312eec8ac4e5a420b6d2ead06b20944017b8d11eb0f362c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc952d356231183ebb550ac17ac54fc4168cad6ccc1d12ebeda2b51ce856d730 0.600000000000 1615973 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": 1132944, "vin": [ { "gen": { "height": 1132934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc952d356231183ebb550ac17ac54fc4168cad6ccc1d12ebeda2b51ce856d730" } } ], "extra": [ 1, 122, 102, 198, 104, 212, 64, 156, 180, 179, 18, 238, 200, 172, 78, 90, 66, 11, 109, 46, 173, 6, 178, 9, 68, 1, 123, 141, 17, 235, 15, 54, 44, 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