Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765cb746b3e8080ba0a7cf1b9d4f5d563ad5a3a7d8310fbf895d5df3f3f310dc

Tx prefix hash: f79366ab0d65e5f6516d554351fe03c98231ddde49612645fb736deaec77d258
Tx public key: 67c2cde8842a9450eda615654c5378f2de571b87ba3536d96a3164f4aaa86e3f
Timestamp: 1730274144 Timestamp [UCT]: 2024-10-30 07:42:24 Age [y:d:h:m:s]: 00:008:05:29:40
Block: 1142666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5882 RingCT/type: yes/0
Extra: 0167c2cde8842a9450eda615654c5378f2de571b87ba3536d96a3164f4aaa86e3f021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 731d2d693041b65fcbf7df6b70c13c674d80fdae32e25dbf5b8f7516fd9f23d9 0.600000000000 1626521 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 dinasty-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": 1142676, "vin": [ { "gen": { "height": 1142666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "731d2d693041b65fcbf7df6b70c13c674d80fdae32e25dbf5b8f7516fd9f23d9" } } ], "extra": [ 1, 103, 194, 205, 232, 132, 42, 148, 80, 237, 166, 21, 101, 76, 83, 120, 242, 222, 87, 27, 135, 186, 53, 54, 217, 106, 49, 100, 244, 170, 168, 110, 63, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8