Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bad38f521e940f4dea9465e4f99ae6097b8a2bdc8c13d9cad9e825bd94ccf45

Tx prefix hash: 90fe5d7dc3abf455fda4d20918de185aafdca9b909e30b56bcf9c1cb0543b2c2
Tx public key: 2b86ce0b792775e590358d71e53d601989f73b23c2e24d1b53dcdff3365f8e89
Timestamp: 1767479703 Timestamp [UTC]: 2026-01-03 22:35:03 Age [y:d:h:m:s]: 00:044:06:58:36
Block: 1448053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 31501 RingCT/type: yes/0
Extra: 012b86ce0b792775e590358d71e53d601989f73b23c2e24d1b53dcdff3365f8e89020900000006f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 771eea4a34928010ba5f4c7b878e27dd73e8c051c0ff7a19a8f9b5d910e5bf60 0.000600000000 1937017 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": 1448063, "vin": [ { "gen": { "height": 1448053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "771eea4a34928010ba5f4c7b878e27dd73e8c051c0ff7a19a8f9b5d910e5bf60" } } ], "extra": [ 1, 43, 134, 206, 11, 121, 39, 117, 229, 144, 53, 141, 113, 229, 61, 96, 25, 137, 247, 59, 35, 194, 226, 77, 27, 83, 220, 223, 243, 54, 95, 142, 137, 2, 9, 0, 0, 0, 6, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


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