Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9b9e66aad18023d158c05eb56bcb57d58986b9c90e77ad5b7c11cdcf30ac7a

Tx prefix hash: cb2689f15f5bb74ccd9c256120f10e2f32bd317406cc95f41119ae6f1ec10c71
Tx public key: e4c2d67291b551ec61601e2540b2a5bd09e11f68c5cd7f451bf503d67ec184c5
Timestamp: 1769453519 Timestamp [UTC]: 2026-01-26 18:51:59 Age [y:d:h:m:s]: 00:298:22:08:01
Block: 1464223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219271 RingCT/type: yes/0
Extra: 01e4c2d67291b551ec61601e2540b2a5bd09e11f68c5cd7f451bf503d67ec184c502110000000349d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a68af8f74c9c4ba88247c96a94a0eac3f0a93ef4bd4ac87907d48f93aed7bbf 0.000600000000 1953447 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": 1464233, "vin": [ { "gen": { "height": 1464223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a68af8f74c9c4ba88247c96a94a0eac3f0a93ef4bd4ac87907d48f93aed7bbf" } } ], "extra": [ 1, 228, 194, 214, 114, 145, 181, 81, 236, 97, 96, 30, 37, 64, 178, 165, 189, 9, 225, 31, 104, 197, 205, 127, 69, 27, 245, 3, 214, 126, 193, 132, 197, 2, 17, 0, 0, 0, 3, 73, 215, 62, 152, 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: