Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fd536c5ec895de00f687a629d20f24ee9ef08a0c5510ca5dd2e613b32496842

Tx prefix hash: c256e3e90d2a9349d27f1639b47f571c8f4e4c0bbc3972d6432d44111df2f14c
Tx public key: 1b820eff5e678f23c542b113181e1256df1d1a0ef3be083d97dd88d5ed78b4fc
Timestamp: 1767550569 Timestamp [UTC]: 2026-01-04 18:16:09 Age [y:d:h:m:s]: 00:042:15:29:02
Block: 1448644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 30318 RingCT/type: yes/0
Extra: 011b820eff5e678f23c542b113181e1256df1d1a0ef3be083d97dd88d5ed78b4fc020900000007f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 785f5931cb4bb3124b25c82f21237da9e96fad18f7471f312453d593dfc94cec 0.000600000000 1937620 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": 1448654, "vin": [ { "gen": { "height": 1448644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "785f5931cb4bb3124b25c82f21237da9e96fad18f7471f312453d593dfc94cec" } } ], "extra": [ 1, 27, 130, 14, 255, 94, 103, 143, 35, 197, 66, 177, 19, 24, 30, 18, 86, 223, 29, 26, 14, 243, 190, 8, 61, 151, 221, 136, 213, 237, 120, 180, 252, 2, 9, 0, 0, 0, 7, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


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