Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d1366aa6364e0cf76dd004fb2000befdc428af212e623ee9d9caace8478a7a

Tx prefix hash: 2275401e67fc246e1a136523664d765eb3d6e02d70b9bbc57b07e0af5f4f70ef
Tx public key: 02fd090b11d2e1a9d1e94c3a2f5f02c27b2981b46b3c1791fb20ec47d32ccfa7
Timestamp: 1727338746 Timestamp [UCT]: 2024-09-26 08:19:06 Age [y:d:h:m:s]: 00:219:20:09:31
Block: 1118398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156940 RingCT/type: yes/0
Extra: 0102fd090b11d2e1a9d1e94c3a2f5f02c27b2981b46b3c1791fb20ec47d32ccfa702110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 238c20c7b8e05eb8541820a1d3fce564d921c56e293aae4087172abc562e6cf9 0.600000000000 1599579 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": 1118408, "vin": [ { "gen": { "height": 1118398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "238c20c7b8e05eb8541820a1d3fce564d921c56e293aae4087172abc562e6cf9" } } ], "extra": [ 1, 2, 253, 9, 11, 17, 210, 225, 169, 209, 233, 76, 58, 47, 95, 2, 194, 123, 41, 129, 180, 107, 60, 23, 145, 251, 32, 236, 71, 211, 44, 207, 167, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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