Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f44d508bb93e2c7926eb251d62896f7bfa894b4b44386f1c91511159ac98350

Tx prefix hash: a3c02c099015d310895398095e891fa2df095a6e40d443198efacc9c8da96e8d
Tx public key: de2f5428d3303b0a835dad63eca7d3f956d5bf8c7477d7c5239ff4c1c12b020f
Timestamp: 1736848032 Timestamp [UCT]: 2025-01-14 09:47:12 Age [y:d:h:m:s]: 00:155:01:06:17
Block: 1197098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110512 RingCT/type: yes/0
Extra: 01de2f5428d3303b0a835dad63eca7d3f956d5bf8c7477d7c5239ff4c1c12b020f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e03d83d598e746aae6664198c779bfdb7670bdc3a7315907b25379823b45b7 0.600000000000 1683703 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": 1197108, "vin": [ { "gen": { "height": 1197098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e03d83d598e746aae6664198c779bfdb7670bdc3a7315907b25379823b45b7" } } ], "extra": [ 1, 222, 47, 84, 40, 211, 48, 59, 10, 131, 93, 173, 99, 236, 167, 211, 249, 86, 213, 191, 140, 116, 119, 215, 197, 35, 159, 244, 193, 193, 43, 2, 15, 2, 17, 0, 0, 0, 8, 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