Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 599a86dd1e8810b9b3bc95aa073b12447744f26082fe6c2c0706a65e2ca57a90

Tx prefix hash: 9fdaf3ece50ca4353b2c0fe30380a3177e8980f33db5e80c41aebb7cae8fd889
Tx public key: f293de3adc32a2a3500bc5b8453eb0798a1f219c28fa77922ad2f2ae07451ffa
Timestamp: 1751404510 Timestamp [UCT]: 2025-07-01 21:15:10 Age [y:d:h:m:s]: 00:142:06:47:36
Block: 1316793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99898 RingCT/type: yes/0
Extra: 01f293de3adc32a2a3500bc5b8453eb0798a1f219c28fa77922ad2f2ae07451ffa0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 679c2a59b3d94c9675fd857588652e23da7282bd544a26b39f52a4ae5c4b1b41 0.600000000000 1804456 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": 1316803, "vin": [ { "gen": { "height": 1316793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "679c2a59b3d94c9675fd857588652e23da7282bd544a26b39f52a4ae5c4b1b41" } } ], "extra": [ 1, 242, 147, 222, 58, 220, 50, 162, 163, 80, 11, 197, 184, 69, 62, 176, 121, 138, 31, 33, 156, 40, 250, 119, 146, 42, 210, 242, 174, 7, 69, 31, 250, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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