Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a656b8f9be10adcb513c6431f3145eb6b96de287905da23b4554dbae35f23b3e

Tx prefix hash: 38cb72def92fc97f2a3c7dc4b98463146e47cf40bd6653c6b851ea02661eb30e
Tx public key: faa1a14c8346730ef833c57861a67dad07f0a1d6d1224842de21a59b1550023e
Timestamp: 1745618440 Timestamp [UTC]: 2025-04-25 22:00:40 Age [y:d:h:m:s]: 01:206:12:24:21
Block: 1269431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411635 RingCT/type: yes/0
Extra: 01faa1a14c8346730ef833c57861a67dad07f0a1d6d1224842de21a59b1550023e02110000002a6c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1bb9218aa5c60dfbd3917c4c6791762e5b452848fa803ecf23189d190f94c9ff 0.000600000000 1756670 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": 1269441, "vin": [ { "gen": { "height": 1269431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb9218aa5c60dfbd3917c4c6791762e5b452848fa803ecf23189d190f94c9ff" } } ], "extra": [ 1, 250, 161, 161, 76, 131, 70, 115, 14, 248, 51, 197, 120, 97, 166, 125, 173, 7, 240, 161, 214, 209, 34, 72, 66, 222, 33, 165, 155, 21, 80, 2, 62, 2, 17, 0, 0, 0, 42, 108, 152, 170, 61, 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: