Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be021d9ba17339f0c756d261a65b4e85b17d8ff4c603270e2d0d36085657d1c2

Tx prefix hash: 4f85036e3ed76ca67c231854a9e22ed7d0e8322ef054776f66522bdbdb7eb543
Tx public key: 1abd4759ca924a54253700d3c6c3dccf03b7c9bf054ddfc1e03d7628fb52407e
Timestamp: 1772844393 Timestamp [UTC]: 2026-03-07 00:46:33 Age [y:d:h:m:s]: 00:252:18:00:03
Block: 1492300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186034 RingCT/type: yes/0
Extra: 011abd4759ca924a54253700d3c6c3dccf03b7c9bf054ddfc1e03d7628fb52407e021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6f5b680b267b2f3ce01070846c4bd31c14759c6753e6c2fcd1170c614f9479d9 0.000600000000 1981842 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": 1492310, "vin": [ { "gen": { "height": 1492300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f5b680b267b2f3ce01070846c4bd31c14759c6753e6c2fcd1170c614f9479d9" } } ], "extra": [ 1, 26, 189, 71, 89, 202, 146, 74, 84, 37, 55, 0, 211, 198, 195, 220, 207, 3, 183, 201, 191, 5, 77, 223, 193, 224, 61, 118, 40, 251, 82, 64, 126, 2, 17, 0, 0, 0, 6, 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: