Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aedefab0806ba22f79d194567e22ebe5cef29e06a8b1e5923a142693aaa0c8e5

Tx prefix hash: 9573dcb525346ae6d80512ba683ba9b01d2d0b3afb7d773448d8638fc4c5ee8f
Tx public key: bc01226cd15d4fe52c70a42fccb94d6806e00963a8f46754f6d3a7a835f4c6e1
Timestamp: 1771862525 Timestamp [UTC]: 2026-02-23 16:02:05 Age [y:d:h:m:s]: 00:268:15:05:19
Block: 1484170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197544 RingCT/type: yes/0
Extra: 01bc01226cd15d4fe52c70a42fccb94d6806e00963a8f46754f6d3a7a835f4c6e1021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7d0b56920bc8a48279e648696d4aaf1b131be0e61d0b1917024667db1a84e04 0.000600000000 1973588 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": 1484180, "vin": [ { "gen": { "height": 1484170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d0b56920bc8a48279e648696d4aaf1b131be0e61d0b1917024667db1a84e04" } } ], "extra": [ 1, 188, 1, 34, 108, 209, 93, 79, 229, 44, 112, 164, 47, 204, 185, 77, 104, 6, 224, 9, 99, 168, 244, 103, 84, 246, 211, 167, 168, 53, 244, 198, 225, 2, 17, 0, 0, 0, 9, 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: