Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f134ff2a764036195656c210319aa6a67adf918d44182626d73e95611be7cbd

Tx prefix hash: e334d24797e41e459220b80e402a61cede065ee60ebd354107b4d0e993a8eb63
Tx public key: 686c94c7e0cb665e11b96eafca38dd2c60bb96333ae3314dddf42969cb8c419d
Timestamp: 1774879386 Timestamp [UTC]: 2026-03-30 14:03:06 Age [y:d:h:m:s]: 00:042:13:51:03
Block: 1509130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22689 RingCT/type: yes/0
Extra: 01686c94c7e0cb665e11b96eafca38dd2c60bb96333ae3314dddf42969cb8c419d0211000000032773ca4d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1623f5bfcb86095950d98196cb4fc0668b38397586017cbb7ad5a1ab3d7b2889 0.000600000000 1998898 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": 1509140, "vin": [ { "gen": { "height": 1509130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1623f5bfcb86095950d98196cb4fc0668b38397586017cbb7ad5a1ab3d7b2889" } } ], "extra": [ 1, 104, 108, 148, 199, 224, 203, 102, 94, 17, 185, 110, 175, 202, 56, 221, 44, 96, 187, 150, 51, 58, 227, 49, 77, 221, 244, 41, 105, 203, 140, 65, 157, 2, 17, 0, 0, 0, 3, 39, 115, 202, 77, 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: