Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec27f8d25ec7421e6fd2cacbc9abfdb8b668fe715f26794897276880f926bb09

Tx prefix hash: 65626557a4aa53ed0c920f56bbbdb3d012602657dce2da97b4414ce9fbfa9135
Tx public key: a51e68c019a53cf5610e59014e48c5df8198a6fea1cd429d8ffd600fadea8c40
Timestamp: 1741380837 Timestamp [UCT]: 2025-03-07 20:53:57 Age [y:d:h:m:s]: 00:259:02:29:00
Block: 1234355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182918 RingCT/type: yes/0
Extra: 01a51e68c019a53cf5610e59014e48c5df8198a6fea1cd429d8ffd600fadea8c400211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc52dc02fe72e840007e2f83b5b191cf9e9793f1df17a2d17213661ff6adb110 0.600000000000 1721282 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": 1234365, "vin": [ { "gen": { "height": 1234355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc52dc02fe72e840007e2f83b5b191cf9e9793f1df17a2d17213661ff6adb110" } } ], "extra": [ 1, 165, 30, 104, 192, 25, 165, 60, 245, 97, 14, 89, 1, 78, 72, 197, 223, 129, 152, 166, 254, 161, 205, 66, 157, 143, 253, 96, 15, 173, 234, 140, 64, 2, 17, 0, 0, 0, 1, 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