Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8601f430b0bcdf7f6103afd32f57c5953ddac4f7a32e32debea71575b840278

Tx prefix hash: 7e5cfc70d240da05470d73533e1b97d0cc82997c35befbe89aad263993c40bad
Tx public key: 3c48d574c11aff2b0dcc692fdffc9d816c410499e88d128a646dc5a5338d4546
Timestamp: 1732768863 Timestamp [UCT]: 2024-11-28 04:41:03 Age [y:d:h:m:s]: 00:112:18:33:55
Block: 1163318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80422 RingCT/type: yes/0
Extra: 013c48d574c11aff2b0dcc692fdffc9d816c410499e88d128a646dc5a5338d45460211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b962c899c9ae5338a5e2f3615810db169d976096e16f9823c4d335fee701cc 0.600000000000 1648985 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": 1163328, "vin": [ { "gen": { "height": 1163318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b962c899c9ae5338a5e2f3615810db169d976096e16f9823c4d335fee701cc" } } ], "extra": [ 1, 60, 72, 213, 116, 193, 26, 255, 43, 13, 204, 105, 47, 223, 252, 157, 129, 108, 65, 4, 153, 232, 141, 18, 138, 100, 109, 197, 165, 51, 141, 69, 70, 2, 17, 0, 0, 0, 3, 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