Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6767640b0623f2df3b32cfdc5639cfd831961fbd6d1893601e7b0e8d6a61323b

Tx prefix hash: 52e266dc9ab08cd697c72d63cf5f890c6022f83af74d89ee61653e2d15c22090
Tx public key: 789f0c2b3200ec0289324a3ca9cab09b8df930d3e783f31f556dc247cf8c0071
Timestamp: 1737215164 Timestamp [UCT]: 2025-01-18 15:46:04 Age [y:d:h:m:s]: 00:150:23:59:16
Block: 1200100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107654 RingCT/type: yes/0
Extra: 01789f0c2b3200ec0289324a3ca9cab09b8df930d3e783f31f556dc247cf8c00710211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eaa8137c6001069a4b7dc2506b8cf3cae193110e7b6b9534204091080a748e0 0.600000000000 1686741 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": 1200110, "vin": [ { "gen": { "height": 1200100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eaa8137c6001069a4b7dc2506b8cf3cae193110e7b6b9534204091080a748e0" } } ], "extra": [ 1, 120, 159, 12, 43, 50, 0, 236, 2, 137, 50, 74, 60, 169, 202, 176, 155, 141, 249, 48, 211, 231, 131, 243, 31, 85, 109, 194, 71, 207, 140, 0, 113, 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