Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b52b7befff51da3b60508614d272b84f88c5bbd1b87f8cf41a702c18dfb372

Tx prefix hash: d904d4046a57f608e3698a911062eb805877083b0dfc9ac8ea870c98e9c819ef
Tx public key: be231dd50a17db350124c623def72560f1b79fa6543c71756dcee6bb693f1dad
Timestamp: 1771232616 Timestamp [UTC]: 2026-02-16 09:03:36 Age [y:d:h:m:s]: 00:273:19:15:40
Block: 1478949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201187 RingCT/type: yes/0
Extra: 01be231dd50a17db350124c623def72560f1b79fa6543c71756dcee6bb693f1dad021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9fa67d2b50ed025aa0dca8f500a2b51553eb18ef874de466576a69d76c172f93 0.000600000000 1968281 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": 1478959, "vin": [ { "gen": { "height": 1478949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa67d2b50ed025aa0dca8f500a2b51553eb18ef874de466576a69d76c172f93" } } ], "extra": [ 1, 190, 35, 29, 213, 10, 23, 219, 53, 1, 36, 198, 35, 222, 247, 37, 96, 241, 183, 159, 166, 84, 60, 113, 117, 109, 206, 230, 187, 105, 63, 29, 173, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: