Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b93d3e298bbc64dec022065a397e92ac401b067bda3485410eeda76c60951c57

Tx prefix hash: d361db5bfb0302b7ebfbcac55126659824e48d3adec50535549b2e0744a6a9dc
Tx public key: c527cd82a1c2b7d513958bf2f3b4084c34a114c93b107ebf339c0f68be2ed1bb
Timestamp: 1719210390 Timestamp [UCT]: 2024-06-24 06:26:30 Age [y:d:h:m:s]: 00:347:01:06:55
Block: 1051002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248052 RingCT/type: yes/0
Extra: 01c527cd82a1c2b7d513958bf2f3b4084c34a114c93b107ebf339c0f68be2ed1bb02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370798a938f3fc473c4d50e03946973aa0ad7f8fb642f44ce57f2f8c62197f17 0.600000000000 1521181 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": 1051012, "vin": [ { "gen": { "height": 1051002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370798a938f3fc473c4d50e03946973aa0ad7f8fb642f44ce57f2f8c62197f17" } } ], "extra": [ 1, 197, 39, 205, 130, 161, 194, 183, 213, 19, 149, 139, 242, 243, 180, 8, 76, 52, 161, 20, 201, 59, 16, 126, 191, 51, 156, 15, 104, 190, 46, 209, 187, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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