Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e50357f84dc31ba2a053eef2c5fca241a9705eed519ee2cafb89c1e0b00239

Tx prefix hash: cbfd80902f28203a5edc10b322bb72614a5aa70f03a76b2ed699a22ee4857e96
Tx public key: efd360ffef7ec9343880adeb11ba482d8dae80586b67ac68aa49b4d76087a041
Timestamp: 1759317427 Timestamp [UTC]: 2025-10-01 11:17:07 Age [y:d:h:m:s]: 01:047:06:43:10
Block: 1380394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300151 RingCT/type: yes/0
Extra: 01efd360ffef7ec9343880adeb11ba482d8dae80586b67ac68aa49b4d76087a04102110000000297baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0eae2d980ca3e199d530f7a7d72c7590660e270372e4d1eda578d4fc475ca34f 0.000600000000 1868505 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": 1380404, "vin": [ { "gen": { "height": 1380394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eae2d980ca3e199d530f7a7d72c7590660e270372e4d1eda578d4fc475ca34f" } } ], "extra": [ 1, 239, 211, 96, 255, 239, 126, 201, 52, 56, 128, 173, 235, 17, 186, 72, 45, 141, 174, 128, 88, 107, 103, 172, 104, 170, 73, 180, 215, 96, 135, 160, 65, 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): devel-2026-02-02-6303d2a (1.2) | monero version: