Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 687360c60af503497265c4458b09f3caefff3a8aeb522063afe936696b327fd3

Tx prefix hash: c6709bd6a5d787ad47a4cb5ed33cc5a8147a2b2f447aa520aa57fde65e7c6c38
Tx public key: f58336b39bb1e6b24dd6afb0191ebfd37313c468592d037006a09cf7069320f3
Timestamp: 1759579357 Timestamp [UCT]: 2025-10-04 12:02:37 Age [y:d:h:m:s]: 00:003:21:53:06
Block: 1382571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2789 RingCT/type: yes/0
Extra: 01f58336b39bb1e6b24dd6afb0191ebfd37313c468592d037006a09cf7069320f302110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05e6c0b4509c7f62c3ca7017dc411d4fe8dbbba0a2b883bec9c8f98bbd5cc2c6 0.600000000000 1870706 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": 1382581, "vin": [ { "gen": { "height": 1382571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e6c0b4509c7f62c3ca7017dc411d4fe8dbbba0a2b883bec9c8f98bbd5cc2c6" } } ], "extra": [ 1, 245, 131, 54, 179, 155, 177, 230, 178, 77, 214, 175, 176, 25, 30, 191, 211, 115, 19, 196, 104, 89, 45, 3, 112, 6, 160, 156, 247, 6, 147, 32, 243, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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