Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcccaf4ad75d08d2b579fa74a05cd41814c0c3620298b5416c026d57dc59e7b2

Tx prefix hash: cd5e20e331383f8c7c75d6ac4be07f49e4dd0ef9405df6b1a920691fe2dd6bd9
Tx public key: a0f487b8195410d8d92a711d2b8f4d0126d456bd10f22fc1af8927c05c99b3d1
Timestamp: 1773964169 Timestamp [UTC]: 2026-03-19 23:49:29 Age [y:d:h:m:s]: 00:051:14:54:32
Block: 1501542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29611 RingCT/type: yes/0
Extra: 01a0f487b8195410d8d92a711d2b8f4d0126d456bd10f22fc1af8927c05c99b3d1021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 996f492fc58d1045e3a02f3f6dde137d1f793978d1ba9ab1787c87c3592e8342 0.000600000000 1991226 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": 1501552, "vin": [ { "gen": { "height": 1501542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "996f492fc58d1045e3a02f3f6dde137d1f793978d1ba9ab1787c87c3592e8342" } } ], "extra": [ 1, 160, 244, 135, 184, 25, 84, 16, 216, 217, 42, 113, 29, 43, 143, 77, 1, 38, 212, 86, 189, 16, 242, 47, 193, 175, 137, 39, 192, 92, 153, 179, 209, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: