Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f5782f1eaf02c469fbc99cd9b2027ef63e2ca2bf43abd75d8e1022c77451ec

Tx prefix hash: a68c7cf1ffeaa5d36c34aab659e63a3bb175ffa2c2cda1a205b2e9138e0a7f2e
Tx public key: d48ae1ee87a4ef3e97b56e7e0694b717fece2fb4325e3582cee083e56162c222
Timestamp: 1774822315 Timestamp [UTC]: 2026-03-29 22:11:55 Age [y:d:h:m:s]: 00:234:12:18:25
Block: 1508647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173173 RingCT/type: yes/0
Extra: 01d48ae1ee87a4ef3e97b56e7e0694b717fece2fb4325e3582cee083e56162c222021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b93beee826ea05bb891b795dc5939bad15ad41b81e91ea7feaa191a542b5cc0d 0.000600000000 1998401 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": 1508657, "vin": [ { "gen": { "height": 1508647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b93beee826ea05bb891b795dc5939bad15ad41b81e91ea7feaa191a542b5cc0d" } } ], "extra": [ 1, 212, 138, 225, 238, 135, 164, 239, 62, 151, 181, 110, 126, 6, 148, 183, 23, 254, 206, 47, 180, 50, 94, 53, 130, 206, 224, 131, 229, 97, 98, 194, 34, 2, 17, 0, 0, 0, 1, 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: