Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 846c12c8bebacb2dc5bb04b9d52c1937bdbe77a9b5879a655aeb5ac4eb73d11d

Tx prefix hash: 4d003fd5538837085d981d92165b8cc2f618e09402ce1a0c627723a5950cef9b
Tx public key: f90e509504b718c0238946d1e393fe346f562ac3dc7111145deab523c32d97d8
Timestamp: 1753863097 Timestamp [UCT]: 2025-07-30 08:11:37 Age [y:d:h:m:s]: 00:099:17:31:52
Block: 1336507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70095 RingCT/type: yes/0
Extra: 01f90e509504b718c0238946d1e393fe346f562ac3dc7111145deab523c32d97d80211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86aa0f1c69bc8e35e4c6ea0a3e619abcbb599ee93c42aa70ddddad8d42d39135 0.600000000000 1824308 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": 1336517, "vin": [ { "gen": { "height": 1336507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86aa0f1c69bc8e35e4c6ea0a3e619abcbb599ee93c42aa70ddddad8d42d39135" } } ], "extra": [ 1, 249, 14, 80, 149, 4, 183, 24, 192, 35, 137, 70, 209, 227, 147, 254, 52, 111, 86, 42, 195, 220, 113, 17, 20, 93, 234, 181, 35, 195, 45, 151, 216, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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