Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb8fcacadd9edc36289fdb6c2f3f0d4e969bc5be91f894043efcedc9acb84da6

Tx prefix hash: d9c78d482f6031c8698612203fe637dbc0cdd670c2472f5a765a796a4381d510
Tx public key: f9e4d6d24ecb8b86049036ca02686ebe0d703930f701b296428145456e3580ba
Timestamp: 1744270348 Timestamp [UTC]: 2025-04-10 07:32:28 Age [y:d:h:m:s]: 01:218:10:24:26
Block: 1258270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420035 RingCT/type: yes/0
Extra: 01f9e4d6d24ecb8b86049036ca02686ebe0d703930f701b296428145456e3580ba0211000000062609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 86140101c0a7fd915cb8af3ed63489e11275e5cb6b36bd7fcb12c74f8bc9b9b2 0.000600000000 1745403 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": 1258280, "vin": [ { "gen": { "height": 1258270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86140101c0a7fd915cb8af3ed63489e11275e5cb6b36bd7fcb12c74f8bc9b9b2" } } ], "extra": [ 1, 249, 228, 214, 210, 78, 203, 139, 134, 4, 144, 54, 202, 2, 104, 110, 190, 13, 112, 57, 48, 247, 1, 178, 150, 66, 129, 69, 69, 110, 53, 128, 186, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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: