Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4f6403654c4d87ca4acba703d440fd2caa972f4fd384861692d1c42a0c42cb

Tx prefix hash: 1f46b894cc56485c1dab3a6499a8abddc7666c210b4908d51302f41847e017e7
Tx public key: d3630563fafe4ab86c45188eabd2e845108ea256ce14e324298c274eee80b225
Timestamp: 1770371702 Timestamp [UTC]: 2026-02-06 09:55:02 Age [y:d:h:m:s]: 00:098:03:56:15
Block: 1471860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62539 RingCT/type: yes/0
Extra: 01d3630563fafe4ab86c45188eabd2e845108ea256ce14e324298c274eee80b225021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 82edcdd2226c2134a651b0f23ceb1483d3df1ed8500e82d83590e1eb8bd67fad 0.000600000000 1961136 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": 1471870, "vin": [ { "gen": { "height": 1471860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82edcdd2226c2134a651b0f23ceb1483d3df1ed8500e82d83590e1eb8bd67fad" } } ], "extra": [ 1, 211, 99, 5, 99, 250, 254, 74, 184, 108, 69, 24, 142, 171, 210, 232, 69, 16, 142, 162, 86, 206, 20, 227, 36, 41, 140, 39, 78, 238, 128, 178, 37, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: