Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee536d4d647a5fba04340ccc950a01a245b1f8e942649e89eef7dba7d906033b

Tx prefix hash: 5e0f09470be7cb63d66f0ed67c70ec43c5f859e5f4904a24112cb3ac8034ca8d
Tx public key: 138b306bae2454843c843faef5d4c51949b2d5ddc3ca625eb961d75be87c9422
Timestamp: 1749593725 Timestamp [UCT]: 2025-06-10 22:15:25 Age [y:d:h:m:s]: 00:157:01:53:06
Block: 1302342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109948 RingCT/type: yes/0
Extra: 01138b306bae2454843c843faef5d4c51949b2d5ddc3ca625eb961d75be87c9422021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b750a6b3fdde4d4713e98a52008da0e74533591c4b5d596ecf894530a7d1916f 0.600000000000 1789911 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": 1302352, "vin": [ { "gen": { "height": 1302342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b750a6b3fdde4d4713e98a52008da0e74533591c4b5d596ecf894530a7d1916f" } } ], "extra": [ 1, 19, 139, 48, 107, 174, 36, 84, 132, 60, 132, 63, 174, 245, 212, 197, 25, 73, 178, 213, 221, 195, 202, 98, 94, 185, 97, 215, 91, 232, 124, 148, 34, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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