Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c0fe6a2c0180f0b853cdad4467d9b151bea4c17a2b7fa2a6d91572c0850723

Tx prefix hash: 35e8545f2c48bc88a895fac4510cf56b67c7dc34ae739153ac25ae5a13ffc592
Tx public key: 185b61431e71e9e150733df189657074c1752b2452134e9b281becd6d262af88
Timestamp: 1766619730 Timestamp [UTC]: 2025-12-24 23:42:10 Age [y:d:h:m:s]: 00:332:03:02:20
Block: 1440909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242585 RingCT/type: yes/0
Extra: 01185b61431e71e9e150733df189657074c1752b2452134e9b281becd6d262af880211000000017b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6bf0795ee7ee291a8149fc63e386729355db8f51d1e376adcbf49ddd19c37941 0.000600000000 1929800 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": 1440919, "vin": [ { "gen": { "height": 1440909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bf0795ee7ee291a8149fc63e386729355db8f51d1e376adcbf49ddd19c37941" } } ], "extra": [ 1, 24, 91, 97, 67, 30, 113, 233, 225, 80, 115, 61, 241, 137, 101, 112, 116, 193, 117, 43, 36, 82, 19, 78, 155, 40, 27, 236, 214, 210, 98, 175, 136, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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: