Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cf4288a3ee0a758c0dcfcc2be11a74706e4dcfc63c04fb15c77816a81fad645

Tx prefix hash: d8c6d5cc4d70cb258b9985cdb71d20df172fa9e2553aafc3df63b6eb567dedec
Tx public key: aa69316f950a0decd55113ebebae0c054e3c29cd8b089ca4aa99d73c6b5a45ab
Timestamp: 1747752214 Timestamp [UTC]: 2025-05-20 14:43:34 Age [y:d:h:m:s]: 01:123:07:37:47
Block: 1287100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352840 RingCT/type: yes/0
Extra: 01aa69316f950a0decd55113ebebae0c054e3c29cd8b089ca4aa99d73c6b5a45ab0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b4e144ba0b74588ce5bbc365d95b2d6de6d2e06d8149c445e3c29876fb0d5745 0.000600000000 1774567 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": 1287110, "vin": [ { "gen": { "height": 1287100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4e144ba0b74588ce5bbc365d95b2d6de6d2e06d8149c445e3c29876fb0d5745" } } ], "extra": [ 1, 170, 105, 49, 111, 149, 10, 13, 236, 213, 81, 19, 235, 235, 174, 12, 5, 78, 60, 41, 205, 139, 8, 156, 164, 170, 153, 215, 60, 107, 90, 69, 171, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: