Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edde540bc7d859d64722ed5cde40674c9ee9ca975c870572a390819ce6332b05

Tx prefix hash: b9bb5c5c70f3e98fe77ef822a00c31dea29db634ca7eda2e5a62fd9a8df2f43f
Tx public key: 70454ee861e13de9e57004f86528cbcf3812bf45eea411001e372415c39e0b03
Timestamp: 1750810776 Timestamp [UTC]: 2025-06-25 00:19:36 Age [y:d:h:m:s]: 00:236:20:56:39
Block: 1312156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167150 RingCT/type: yes/0
Extra: 0170454ee861e13de9e57004f86528cbcf3812bf45eea411001e372415c39e0b0302110000000301491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4b589a0cb4ddad58fe3abf453fec0af4a0f21f3d95f8bd6601ac71b61a80e06 0.000600000000 1799787 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": 1312166, "vin": [ { "gen": { "height": 1312156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4b589a0cb4ddad58fe3abf453fec0af4a0f21f3d95f8bd6601ac71b61a80e06" } } ], "extra": [ 1, 112, 69, 78, 232, 97, 225, 61, 233, 229, 112, 4, 248, 101, 40, 203, 207, 56, 18, 191, 69, 238, 164, 17, 0, 30, 55, 36, 21, 195, 158, 11, 3, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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) | dinastycoin version: tesla-369