Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed241056ebff3b58b7fc752e0f3202714bbd0747fdca9cc44ad69f03d8d4339d

Tx prefix hash: d60475d2bfb1b63581391876425b49d2b7d8f0fc7606ac9a3bff08b96794e967
Tx public key: 36ef69696388d1ba3e26273712d537e236e8d2b000a708de21f70e029f612662
Timestamp: 1773669297 Timestamp [UTC]: 2026-03-16 13:54:57 Age [y:d:h:m:s]: 00:242:11:02:47
Block: 1499135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178645 RingCT/type: yes/0
Extra: 0136ef69696388d1ba3e26273712d537e236e8d2b000a708de21f70e029f612662021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1148def12f99f9b839d44466619607dc9f4196a63e83fd9e10219f10e3e109df 0.000600000000 1988789 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": 1499145, "vin": [ { "gen": { "height": 1499135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1148def12f99f9b839d44466619607dc9f4196a63e83fd9e10219f10e3e109df" } } ], "extra": [ 1, 54, 239, 105, 105, 99, 136, 209, 186, 62, 38, 39, 55, 18, 213, 55, 226, 54, 232, 210, 176, 0, 167, 8, 222, 33, 247, 14, 2, 159, 97, 38, 98, 2, 17, 0, 0, 0, 8, 241, 136, 200, 168, 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: