Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 514898e42633820f9112ffd801ee6260cb7ddb891b2caa0f82e5cbe7fe6c3ee5

Tx prefix hash: c3eff6f09ed1ef98c98b5897c7c42ff87be21f0e06f19e521670f10352de5468
Tx public key: c21ecd5fe9c86be5ae320c916beec3bac2e6f015f2eeb966c9e596607b2c3d03
Timestamp: 1765871396 Timestamp [UTC]: 2025-12-16 07:49:56 Age [y:d:h:m:s]: 00:336:10:06:27
Block: 1434711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245832 RingCT/type: yes/0
Extra: 01c21ecd5fe9c86be5ae320c916beec3bac2e6f015f2eeb966c9e596607b2c3d03021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f603eb8b8b679a67423de881b308ab70fa8c35ebd74bfccdc9a2fbbed0d04cca 0.000600000000 1923502 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": 1434721, "vin": [ { "gen": { "height": 1434711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f603eb8b8b679a67423de881b308ab70fa8c35ebd74bfccdc9a2fbbed0d04cca" } } ], "extra": [ 1, 194, 30, 205, 95, 233, 200, 107, 229, 174, 50, 12, 145, 107, 238, 195, 186, 194, 230, 240, 21, 242, 238, 185, 102, 201, 229, 150, 96, 123, 44, 61, 3, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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: