Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c5a977321c5e4cb8e223e110109ccc96f83c52fcfc9e987b74bcd69e538176

Tx prefix hash: 7753755eefce405b6d942061fbabd91de8a90478356fc22c97ad5074dae87bea
Tx public key: 366b8def8f66edd08a84fea351df495237a038f7c9417fdc3d7ed13110bb7b6e
Timestamp: 1754259590 Timestamp [UTC]: 2025-08-03 22:19:50 Age [y:d:h:m:s]: 01:107:18:43:32
Block: 1339689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342342 RingCT/type: yes/0
Extra: 01366b8def8f66edd08a84fea351df495237a038f7c9417fdc3d7ed13110bb7b6e021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ff854afe827b50190e40553b428627f56b3e3654957a1c262a954339fa6bbbe 0.000600000000 1827504 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": 1339699, "vin": [ { "gen": { "height": 1339689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff854afe827b50190e40553b428627f56b3e3654957a1c262a954339fa6bbbe" } } ], "extra": [ 1, 54, 107, 141, 239, 143, 102, 237, 208, 138, 132, 254, 163, 81, 223, 73, 82, 55, 160, 56, 247, 201, 65, 127, 220, 61, 126, 209, 49, 16, 187, 123, 110, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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: