Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53afca9e72b092188af235050da40a9d7db1502be8775e986c55fccc60f18d51

Tx prefix hash: 970daa4edf9d642c0c66c46ff0baa422a4bdfbde3afcc6e82143636675c9eb36
Tx public key: a31da6792e2c9de1ccd167abf5c46e2b89a044c818bd1339be3e115f65ebff52
Timestamp: 1633081171 Timestamp [UTC]: 2021-10-01 09:39:31 Age [y:d:h:m:s]: 05:050:12:59:39
Block: 344387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337826 RingCT/type: yes/0
Extra: 01a31da6792e2c9de1ccd167abf5c46e2b89a044c818bd1339be3e115f65ebff520211000000315410958b000000000000000000

1 output(s) for total of 0.044352251724 xmr

stealth address amount amount idx tag
00: 1d0e498c9e76f416023b19ef49bfa79e7a8905dffe433cfb8f69af5c6b434378 0.044352251724 706659 of 0 -

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": 344397, "vin": [ { "gen": { "height": 344387 } } ], "vout": [ { "amount": 44352251724, "target": { "key": "1d0e498c9e76f416023b19ef49bfa79e7a8905dffe433cfb8f69af5c6b434378" } } ], "extra": [ 1, 163, 29, 166, 121, 46, 44, 157, 225, 204, 209, 103, 171, 245, 196, 110, 43, 137, 160, 68, 200, 24, 189, 19, 57, 190, 62, 17, 95, 101, 235, 255, 82, 2, 17, 0, 0, 0, 49, 84, 16, 149, 139, 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: