Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0ebf51c2b8ffcec47eb80ee3d70eb2ac9a32404dcab9277aedc58b4306c5f6a

Tx prefix hash: dd98b47bdc2643b6fb7d51703435ee48ac752407d711f83226b40b3c0df7eeb8
Tx public key: d9fbc29a6a7255b51702de4f96f797f51b6ae65728cb474804230429d6559b9b
Timestamp: 1760391278 Timestamp [UTC]: 2025-10-13 21:34:38 Age [y:d:h:m:s]: 01:031:23:21:45
Block: 1389317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289080 RingCT/type: yes/0
Extra: 01d9fbc29a6a7255b51702de4f96f797f51b6ae65728cb474804230429d6559b9b021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b7d0748a9f7e7d1277f2ad44b95aa3e16b2ae9d1a6aed018092b529c158135ab 0.000600000000 1877546 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 dinastycoin-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": 1389327, "vin": [ { "gen": { "height": 1389317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d0748a9f7e7d1277f2ad44b95aa3e16b2ae9d1a6aed018092b529c158135ab" } } ], "extra": [ 1, 217, 251, 194, 154, 106, 114, 85, 181, 23, 2, 222, 79, 150, 247, 151, 245, 27, 106, 230, 87, 40, 203, 71, 72, 4, 35, 4, 41, 214, 85, 155, 155, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: