Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25fd369d91e6db440910d516fa08eea18f3dad90ef5dec15cc2acd5d1cc944af

Tx prefix hash: e7a599901c80c32229f84e6e5c37e42c13c34912dd0cf722596a8e8493d4416a
Tx public key: d3b5963b010cf0e48f73111178c0f74b5bb729256dc36f6cfe8dce508bed7305
Timestamp: 1755479475 Timestamp [UTC]: 2025-08-18 01:11:15 Age [y:d:h:m:s]: 01:093:10:27:48
Block: 1348870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332985 RingCT/type: yes/0
Extra: 01d3b5963b010cf0e48f73111178c0f74b5bb729256dc36f6cfe8dce508bed7305021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: defa327423d58a34c5b06063a089a3bdcacd6de0e236378fd16b094dbd9700ee 0.000600000000 1836799 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": 1348880, "vin": [ { "gen": { "height": 1348870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "defa327423d58a34c5b06063a089a3bdcacd6de0e236378fd16b094dbd9700ee" } } ], "extra": [ 1, 211, 181, 150, 59, 1, 12, 240, 228, 143, 115, 17, 17, 120, 192, 247, 75, 91, 183, 41, 37, 109, 195, 111, 108, 254, 141, 206, 80, 139, 237, 115, 5, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: