Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f71e997a0dc4e4e00fd3c3322d8e416bbd15ffc76d22f7388975677f255415

Tx prefix hash: ffad355e778d32899a252c280a8660e7d4f0d282c663cdf95c368e113987953d
Tx public key: 745b1661f74ff085fb3d262643079d10a17bdc7900ac01ff5d7ee340b84a861b
Timestamp: 1790542545 Timestamp [UTC]: 2026-09-27 20:55:45 Age [y:d:h:m:s]: 00:046:19:30:59
Block: 1644966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 32548 RingCT/type: yes/0
Extra: 01745b1661f74ff085fb3d262643079d10a17bdc7900ac01ff5d7ee340b84a861b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b210033a4b3121339f3e1ca22ce54fa1db2c7602a9f358103d2b82e7a3066a4d 0.000600000000 2135052 of 15 <0c>

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": 1644976, "vin": [ { "gen": { "height": 1644966 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b210033a4b3121339f3e1ca22ce54fa1db2c7602a9f358103d2b82e7a3066a4d", "view_tag": "0c" } } } ], "extra": [ 1, 116, 91, 22, 97, 247, 79, 240, 133, 251, 61, 38, 38, 67, 7, 157, 16, 161, 123, 220, 121, 0, 172, 1, 255, 93, 126, 227, 64, 184, 74, 134, 27 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: