Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d48b0baa0a42e2840fbf2c5fe399d4be96284ef0a590364526b95f0429d7f6e

Tx prefix hash: 72744e905ea05b881e779fa5cfd1ca28c6d31a57ee4149aa0b91e119533a5975
Tx public key: 056e795d790912cec7ec56f4d01bc51df7690cb3ba622a0d4b1e52776a3b5b25
Timestamp: 1746871952 Timestamp [UTC]: 2025-05-10 10:12:32 Age [y:d:h:m:s]: 01:193:15:41:19
Block: 1279804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402509 RingCT/type: yes/0
Extra: 01056e795d790912cec7ec56f4d01bc51df7690cb3ba622a0d4b1e52776a3b5b250211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6e48f61a59ff26e341e760797e1ea8e850cdd6520b805c9e3f1ede7615f3e239 0.000600000000 1767185 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": 1279814, "vin": [ { "gen": { "height": 1279804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e48f61a59ff26e341e760797e1ea8e850cdd6520b805c9e3f1ede7615f3e239" } } ], "extra": [ 1, 5, 110, 121, 93, 121, 9, 18, 206, 199, 236, 86, 244, 208, 27, 197, 29, 247, 105, 12, 179, 186, 98, 42, 13, 75, 30, 82, 119, 106, 59, 91, 37, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: