Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dfb2b6b1b3bdc29f6df119982a8f5737cfa0c2b983cfd3f3ae353341518b2a5

Tx prefix hash: 8c2d5ebfc33d9ce18b98301a492642ce2a85a879c4c6e6078dce5577d3182be5
Tx public key: e7bd2b6097c1ff58068c8996a270e84209b5420e5cbe647be2f3d289f4621ff5
Timestamp: 1745458610 Timestamp [UTC]: 2025-04-24 01:36:50 Age [y:d:h:m:s]: 01:034:07:52:19
Block: 1268097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277127 RingCT/type: yes/0
Extra: 01e7bd2b6097c1ff58068c8996a270e84209b5420e5cbe647be2f3d289f4621ff50211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78c4a4f36c05d8f5c931de4ae74ab80f791ad4799b4581ae8290d5fc593d5c65 0.000600000000 1755326 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": 1268107, "vin": [ { "gen": { "height": 1268097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78c4a4f36c05d8f5c931de4ae74ab80f791ad4799b4581ae8290d5fc593d5c65" } } ], "extra": [ 1, 231, 189, 43, 96, 151, 193, 255, 88, 6, 140, 137, 150, 162, 112, 232, 66, 9, 181, 66, 14, 92, 190, 100, 123, 226, 243, 210, 137, 244, 98, 31, 245, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: