Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75505faf3b14d857b61f70c2cbbd8bb0620a4939cdee70580ac089627004fce

Tx prefix hash: e05588df3ed1dc0242890c8cbc5f4b34d17590ef9cc5fbafbce9a5791499ab61
Tx public key: 0040382a3bc56044f2f508c8fd1f8b4b8e35b96ab62fd616f141681a1608f7f3
Timestamp: 1743739401 Timestamp [UTC]: 2025-04-04 04:03:21 Age [y:d:h:m:s]: 01:143:03:12:23
Block: 1253866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366657 RingCT/type: yes/0
Extra: 010040382a3bc56044f2f508c8fd1f8b4b8e35b96ab62fd616f141681a1608f7f30211000000034060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f7db764e870ea98f393a267bf39b41c664a1d493eda0f9c264ce96fd78ac053 0.000600000000 1740947 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": 1253876, "vin": [ { "gen": { "height": 1253866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7db764e870ea98f393a267bf39b41c664a1d493eda0f9c264ce96fd78ac053" } } ], "extra": [ 1, 0, 64, 56, 42, 59, 197, 96, 68, 242, 245, 8, 200, 253, 31, 139, 75, 142, 53, 185, 106, 182, 47, 214, 22, 241, 65, 104, 26, 22, 8, 247, 243, 2, 17, 0, 0, 0, 3, 64, 96, 246, 210, 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: