Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0cb2cb48601e7588977282c8d8ad08fde7d722c6e3cf92dc08021c327fa333

Tx prefix hash: 3a04aede00f2fb5f44af65626b06ed041d8b0f248ed4cc247622020c466c8015
Tx public key: 9b2c332a87eea2228812dd064bf2c543c84f0e988ebda2dc9c8a79b45c0a0c79
Timestamp: 1732898083 Timestamp [UCT]: 2024-11-29 16:34:43 Age [y:d:h:m:s]: 00:204:17:40:39
Block: 1164395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145995 RingCT/type: yes/0
Extra: 019b2c332a87eea2228812dd064bf2c543c84f0e988ebda2dc9c8a79b45c0a0c790211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b7041bc3af5609a43414f2f26df3596433a505b020a9df4017e602880c85e0 0.600000000000 1650068 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": 1164405, "vin": [ { "gen": { "height": 1164395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b7041bc3af5609a43414f2f26df3596433a505b020a9df4017e602880c85e0" } } ], "extra": [ 1, 155, 44, 51, 42, 135, 238, 162, 34, 136, 18, 221, 6, 75, 242, 197, 67, 200, 79, 14, 152, 142, 189, 162, 220, 156, 138, 121, 180, 92, 10, 12, 121, 2, 17, 0, 0, 0, 1, 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