Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbf48e951de85fb4eeceac2ba82ec7b0ca3068039c727447467b9f6333d52a8a

Tx prefix hash: 29a4755c14ecd0e53423294344822c7c8de66531711ac7a462a0c4590dc8cd7f
Tx public key: d64bc25a56f3dd4af8ee83a09dcb0750644a97bca32470d93ca53605eee39d99
Timestamp: 1773358305 Timestamp [UTC]: 2026-03-12 23:31:45 Age [y:d:h:m:s]: 00:249:23:05:36
Block: 1496554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184140 RingCT/type: yes/0
Extra: 01d64bc25a56f3dd4af8ee83a09dcb0750644a97bca32470d93ca53605eee39d99021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 54d8be2abc60ea71c096e60fa132c1a4ce428ca59f5bae00fdb2c72ed73be029 0.000600000000 1986180 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": 1496564, "vin": [ { "gen": { "height": 1496554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d8be2abc60ea71c096e60fa132c1a4ce428ca59f5bae00fdb2c72ed73be029" } } ], "extra": [ 1, 214, 75, 194, 90, 86, 243, 221, 74, 248, 238, 131, 160, 157, 203, 7, 80, 100, 74, 151, 188, 163, 36, 112, 217, 60, 165, 54, 5, 238, 227, 157, 153, 2, 17, 0, 0, 0, 2, 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: