Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1841a7bcef7523b1d17101db6d5b9daf1d32ac1a4c1a77032d2d151ecdba6d88

Tx prefix hash: 6cf3f674297204c140e9667da69f2075a13c083207d64db60aa218fb25224edc
Tx public key: 05d20fb21a2976c37229e8ef9cc1df5705ebc2f25287921577f361a8aa316905
Timestamp: 1743007160 Timestamp [UTC]: 2025-03-26 16:39:20 Age [y:d:h:m:s]: 01:237:05:12:47
Block: 1247793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433620 RingCT/type: yes/0
Extra: 0105d20fb21a2976c37229e8ef9cc1df5705ebc2f25287921577f361a8aa316905021100000006d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc606a8a15b32ee65609e7d4c9b5bf94d70746d9a5b417fdb44a89f7cd2a5bb1 0.000600000000 1734820 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": 1247803, "vin": [ { "gen": { "height": 1247793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc606a8a15b32ee65609e7d4c9b5bf94d70746d9a5b417fdb44a89f7cd2a5bb1" } } ], "extra": [ 1, 5, 210, 15, 178, 26, 41, 118, 195, 114, 41, 232, 239, 156, 193, 223, 87, 5, 235, 194, 242, 82, 135, 146, 21, 119, 243, 97, 168, 170, 49, 105, 5, 2, 17, 0, 0, 0, 6, 210, 228, 14, 253, 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: