Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fe98ed7f35dc45afdc2b9e0e4f5368278db11d53e02f238f034c2335ecf7d67

Tx prefix hash: 0e006af35111403846480ec4dfb0dfbfff2f8a5369ecea4d50cefa14fffab602
Tx public key: d3c8fc24436d3f0f4daa7897a7553b951819d8d8aa767cea7b03e9ffe6a0ca48
Timestamp: 1744793877 Timestamp [UTC]: 2025-04-16 08:57:57 Age [y:d:h:m:s]: 01:212:14:29:13
Block: 1262603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415881 RingCT/type: yes/0
Extra: 01d3c8fc24436d3f0f4daa7897a7553b951819d8d8aa767cea7b03e9ffe6a0ca48021100000004dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 83540945c8d6226131cec0869d98c3caabcf4e96e3f5226af17fdb281edbc7f9 0.000600000000 1749784 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": 1262613, "vin": [ { "gen": { "height": 1262603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83540945c8d6226131cec0869d98c3caabcf4e96e3f5226af17fdb281edbc7f9" } } ], "extra": [ 1, 211, 200, 252, 36, 67, 109, 63, 15, 77, 170, 120, 151, 167, 85, 59, 149, 24, 25, 216, 216, 170, 118, 124, 234, 123, 3, 233, 255, 230, 160, 202, 72, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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: