Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b090c40ec88dbd7590b2cb1c6fa876080bf9dcce3db5a38fdfdc46cf8688e63b

Tx prefix hash: 180f3c51e120668a21a1184a8b2fdece36ee443b3e98ab07255c6575c020a611
Tx public key: b32c265bc709f197a5860a3d371ef81d1cf856001d911d52f702453fccc3a4ab
Timestamp: 1746023451 Timestamp [UTC]: 2025-04-30 14:30:51 Age [y:d:h:m:s]: 00:291:04:40:58
Block: 1272778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205751 RingCT/type: yes/0
Extra: 01b32c265bc709f197a5860a3d371ef81d1cf856001d911d52f702453fccc3a4ab02110000000325a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d8ef54fc9649ec5fd90668d16f57cdcd09244a8b3b3b4059c5ca751517d7dae5 0.000600000000 1760053 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": 1272788, "vin": [ { "gen": { "height": 1272778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8ef54fc9649ec5fd90668d16f57cdcd09244a8b3b3b4059c5ca751517d7dae5" } } ], "extra": [ 1, 179, 44, 38, 91, 199, 9, 241, 151, 165, 134, 10, 61, 55, 30, 248, 29, 28, 248, 86, 0, 29, 145, 29, 82, 247, 2, 69, 63, 204, 195, 164, 171, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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) | dinastycoin version: tesla-369