Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f99cba26a6d50be8acc1838871ad917e65ef21bfa5e2daad7a2bdec6319bcb

Tx prefix hash: cf0b9e13a4b04a49cc376e700400762e06e0b5185066d76b89ca2b9782bd143d
Tx public key: b93ae0d2201c024d5f894dcb6821a7de4599bcf8f449501c595ddc4f3780f055
Timestamp: 1771967361 Timestamp [UTC]: 2026-02-24 21:09:21 Age [y:d:h:m:s]: 00:268:07:40:13
Block: 1485045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197361 RingCT/type: yes/0
Extra: 01b93ae0d2201c024d5f894dcb6821a7de4599bcf8f449501c595ddc4f3780f055021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6aa7013eaaed3a20cedc10106cd0470c71734bdf28241cb717ea0134ffb13bc 0.000600000000 1974477 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": 1485055, "vin": [ { "gen": { "height": 1485045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6aa7013eaaed3a20cedc10106cd0470c71734bdf28241cb717ea0134ffb13bc" } } ], "extra": [ 1, 185, 58, 224, 210, 32, 28, 2, 77, 95, 137, 77, 203, 104, 33, 167, 222, 69, 153, 188, 248, 244, 73, 80, 28, 89, 93, 220, 79, 55, 128, 240, 85, 2, 17, 0, 0, 0, 2, 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: