Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3c1c43729595eb7fb2ad09fad14efbceda3e7c93ecb82552d3704ffbaba268

Tx prefix hash: 884b3491371f0413b35cff4649cce00f5fceb7cba9c9fb75d6c83b09c0c7bde4
Tx public key: bd95b8f58251a51286ccf20934148502b32459d957b3881ad05f8a431b0a5ad6
Timestamp: 1775057992 Timestamp [UTC]: 2026-04-01 15:39:52 Age [y:d:h:m:s]: 00:232:04:45:25
Block: 1510599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171539 RingCT/type: yes/0
Extra: 01bd95b8f58251a51286ccf20934148502b32459d957b3881ad05f8a431b0a5ad6021100000004ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 278339c7053cd880f78d8e79a0ea0444e7d80519cd2fd5c71c58a0f3dc0fcf5f 0.000600000000 2000385 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": 1510609, "vin": [ { "gen": { "height": 1510599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "278339c7053cd880f78d8e79a0ea0444e7d80519cd2fd5c71c58a0f3dc0fcf5f" } } ], "extra": [ 1, 189, 149, 184, 245, 130, 81, 165, 18, 134, 204, 242, 9, 52, 20, 133, 2, 179, 36, 89, 217, 87, 179, 136, 26, 208, 95, 138, 67, 27, 10, 90, 214, 2, 17, 0, 0, 0, 4, 238, 75, 113, 129, 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: