Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2f526faedb72143d5206358beef80e793692bafb8152f739d2ece7d6a84cee

Tx prefix hash: 4d435a849d750babe06cfab107e5c1c55e0924682d582d732a40ac08df536e07
Tx public key: 781dff3d95bf812cd10ccd719d632052a342f8cc48e40c6e26cf50383cdaf71a
Timestamp: 1748981815 Timestamp [UTC]: 2025-06-03 20:16:55 Age [y:d:h:m:s]: 01:163:16:17:45
Block: 1297286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380852 RingCT/type: yes/0
Extra: 01781dff3d95bf812cd10ccd719d632052a342f8cc48e40c6e26cf50383cdaf71a02110000000343846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9c507b4a08c33c7f8e69758bd55f9d1c38e8062c6345ab71c674a4e7662aaf63 0.000600000000 1784803 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": 1297296, "vin": [ { "gen": { "height": 1297286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c507b4a08c33c7f8e69758bd55f9d1c38e8062c6345ab71c674a4e7662aaf63" } } ], "extra": [ 1, 120, 29, 255, 61, 149, 191, 129, 44, 209, 12, 205, 113, 157, 99, 32, 82, 163, 66, 248, 204, 72, 228, 12, 110, 38, 207, 80, 56, 60, 218, 247, 26, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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: