Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858bfe01a0b9227bf5f9e0e3be95693e5b53e084d6b672cbbf1ff36ca48c9b93

Tx prefix hash: c83baae2a0252326b6027d94c02f68bbf75231bc4a31684b92301e713d3598b9
Tx public key: 3a201275f8998e4819dd72ac505e8ce84daa76b833768ab77a4ef0bfb1cc765e
Timestamp: 1772311702 Timestamp [UTC]: 2026-02-28 20:48:22 Age [y:d:h:m:s]: 00:265:19:14:41
Block: 1487873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195621 RingCT/type: yes/0
Extra: 013a201275f8998e4819dd72ac505e8ce84daa76b833768ab77a4ef0bfb1cc765e021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fed09c60dfac0eb989844efcdc32f986d804f0d6cd40106b1fe7727be706508e 0.000600000000 1977345 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": 1487883, "vin": [ { "gen": { "height": 1487873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fed09c60dfac0eb989844efcdc32f986d804f0d6cd40106b1fe7727be706508e" } } ], "extra": [ 1, 58, 32, 18, 117, 248, 153, 142, 72, 25, 221, 114, 172, 80, 94, 140, 232, 77, 170, 118, 184, 51, 118, 138, 183, 122, 78, 240, 191, 177, 204, 118, 94, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: