Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16f03213bc4cc59ec5eaaf7f6c948e25ed30d16e50709e9c16b45f25f90ebdd

Tx prefix hash: 6e7818ea4806aa7be755b3fd1b5c20d9c0c23f485e0c38f40bc1af01f5e02563
Tx public key: 2163f9481f2342b3c65f802910d47f9e5075069d72f49c09fc44dc39c7cb340f
Timestamp: 1750810135 Timestamp [UTC]: 2025-06-25 00:08:55 Age [y:d:h:m:s]: 01:146:16:47:28
Block: 1312150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369110 RingCT/type: yes/0
Extra: 012163f9481f2342b3c65f802910d47f9e5075069d72f49c09fc44dc39c7cb340f02110000000843846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d616cb872bcdb91dd1067a8efc8dde1cb71a581bfd92767ff9b48c79e29d0b17 0.000600000000 1799781 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": 1312160, "vin": [ { "gen": { "height": 1312150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d616cb872bcdb91dd1067a8efc8dde1cb71a581bfd92767ff9b48c79e29d0b17" } } ], "extra": [ 1, 33, 99, 249, 72, 31, 35, 66, 179, 198, 95, 128, 41, 16, 212, 127, 158, 80, 117, 6, 157, 114, 244, 156, 9, 252, 68, 220, 57, 199, 203, 52, 15, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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: